From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20425 invoked by uid 1002); 28 Nov 2003 18:54:25 -0000 Mailing-List: contact gentoo-portage-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail Reply-To: gentoo-portage-dev@gentoo.org X-BeenThere: gentoo-portage-dev@gentoo.org Received: (qmail 767 invoked from network); 28 Nov 2003 18:54:24 -0000 From: Daniel Robbins To: gentoo-portage-dev@gentoo.org Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-j8HDgLipELjG3f63/cLh" Organization: Gentoo Technologies, Inc. Message-Id: <1070045720.12096.43.camel@ht.gentoo.org> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Fri, 28 Nov 2003 11:55:21 -0700 Subject: [gentoo-portage-dev] portage-ng requirements doc X-Archives-Salt: ea78cae6-4f07-4dec-9f7d-bb1dc4a38126 X-Archives-Hash: abb3aa3315e9ec3475945f2b00796f1b --=-j8HDgLipELjG3f63/cLh Content-Type: text/plain Content-Transfer-Encoding: quoted-printable 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. --=-j8HDgLipELjG3f63/cLh Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQA/x5oYffezrJ9WV/IRAvAnAJ4ri39kg/QzhyqNQVCiymjWGQIIQgCggk0q YHkpFF5Pz6q0ilDF0s5dvPE= =DCRj -----END PGP SIGNATURE----- --=-j8HDgLipELjG3f63/cLh--