public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel Robbins <drobbins@gentoo.org>
To: gentoo-portage-dev@gentoo.org
Subject: Re: [gentoo-portage-dev] portage-ng requirements doc
Date: Fri, 28 Nov 2003 18:51:03 -0700	[thread overview]
Message-ID: <1070070663.17021.13.camel@ht.gentoo.org> (raw)
In-Reply-To: <200311282315.57449.pauldv@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 743 bytes --]

On Fri, 2003-11-28 at 15:15, Paul de Vrieze wrote:
> implementation goals:

I do not mean any offense by this, but I will continue to
unapologetically reject anything implementation-focused at this point.
Requirements and design goals need to be written in such a way so that
they are not implementation-specific. So, words such as "USEFLAGS,"
"distfiles," "slots" or even "ebuild" should not be used in any of the
requirements, as they have a built-in bias towards a particular
implementation.

Figure out what types of problems you are trying to address in your list
of implementation goals, and distill them to a raw, generic requirement
or design goal. Then I can incorporate them into the design spec.

Regards,

Daniel

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2003-11-29  1:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-28 18:55 [gentoo-portage-dev] portage-ng requirements doc Daniel Robbins
2003-11-28 22:15 ` Paul de Vrieze
2003-11-29  0:47   ` Andrew Gaffney
2003-11-29  1:41     ` Daniel Robbins
2003-11-29  1:51   ` Daniel Robbins [this message]
2003-11-29  2:01 ` Lisa Seelye
2003-11-29  5:01 ` Marius Mauch

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1070070663.17021.13.camel@ht.gentoo.org \
    --to=drobbins@gentoo.org \
    --cc=gentoo-portage-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox