From: Lisa Seelye <lisa@gentoo.org>
To: gentoo-portage-dev@gentoo.org
Subject: Re: [gentoo-portage-dev] portage-ng requirements doc
Date: Fri, 28 Nov 2003 21:01:51 -0500 [thread overview]
Message-ID: <1070071311.32640.136.camel@lisa.thedoh.com> (raw)
In-Reply-To: <1070045720.12096.43.camel@ht.gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 904 bytes --]
On Fri, 2003-11-28 at 13:55, Daniel Robbins wrote:
> Here is a draft of what we are looking for for the comprehensive
> requirements document we need to develop. To help portage-ng
> development, please expand on this document and post your
> additions/improvements to this list. This doc will probably end up being
> 10-15 pages long...
The design specs should be completely standalone from the
implementation. That is, no language specific cruft in the specs.
This, so the user can (if he or she so chooses) rewrite Portage(-ng) on
their own in any capable language.
On a related thread, for the sake of a short dependency tree (both in
code length and number of packages needed) the chosen language should be
a major deciding factor when picking a language to implement the final
project in.
--
Regards,
-Lisa
<Vix ulla tam iniqua pax, quin bello vel aequissimo sit potior>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-11-29 2:00 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
2003-11-29 2:01 ` Lisa Seelye [this message]
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=1070071311.32640.136.camel@lisa.thedoh.com \
--to=lisa@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