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: [gentoo-portage-dev] portage-ng requirements doc
Date: Fri, 28 Nov 2003 11:55:21 -0700	[thread overview]
Message-ID: <1070045720.12096.43.camel@ht.gentoo.org> (raw)

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

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...

portage-ng

This is the specification for portage-ng, a package manager/"ports"
system. portage-ng is intended to be able to perform the following tasks
on an individual host system: downloading sources or pre-compiled
packages from the Internet, configuration, compilation and installation
of sources according to user requirements, general package management.
In addition, portage-ng should be able to be easily extended to perform
tasks that would be expected of it in an enterprise, cluster, or other
kind of environment, which may include management of groups of systems
over the network.

architecture requirements:

1) facilitate parallel, community development
2) allow for easy extensibility and new feature additions over time
3) provide a coherent model for (meta)data representation and storage
4) will run on a wide variety of systems
5) will run efficiently even on modest hardware
6) in as much as possible, encourage and/or enforce the development of
high-quality, versatile and maintainable code
7) encourage/enforce separation of package metadata from specific build
steps and algorithms
8) allow for delivery of feature set that meets or exceeds expectations
of existing user community

design goals:

1) reflect the sensibilities of "ports" system designs
2) provide an easy-to-understand developer API
3) provide an open, transparent architecture that reflects UNIX design
philosophy
4) In every way possible, program should be malleable to allow
conformation to user needs and expectations,
both interface as well as the specific actions performed by the program.






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

             reply	other threads:[~2003-11-28 18:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-28 18:55 Daniel Robbins [this message]
2003-11-28 22:15 ` [gentoo-portage-dev] portage-ng requirements doc 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
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=1070045720.12096.43.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