From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26318 invoked from network); 16 Jul 2004 08:49:55 +0000 Received: from smtp.gentoo.org (156.56.111.197) by lists.gentoo.org with AES256-SHA encrypted SMTP; 16 Jul 2004 08:49:55 +0000 Received: from lists.gentoo.org ([156.56.111.196] helo=parrot.gentoo.org) by smtp.gentoo.org with esmtp (Exim 4.34) id 1BlOPh-0001Uk-9Z for arch-gentoo-portage-dev@lists.gentoo.org; Fri, 16 Jul 2004 08:49:53 +0000 Received: (qmail 11530 invoked by uid 89); 16 Jul 2004 08:49:52 +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@lists.gentoo.org X-BeenThere: gentoo-portage-dev@gentoo.org Received: (qmail 20608 invoked from network); 16 Jul 2004 08:49:51 +0000 Message-ID: <40F796A6.3080108@wanadoo.fr> Date: Fri, 16 Jul 2004 10:49:42 +0200 From: =?ISO-8859-1?Q?Philippe_Lafoucri=E8re?= Reply-To: lafou@wanadoo.fr Organization: Zeni Corporation User-Agent: Mozilla Thunderbird 0.6 (X11/20040703) X-Accept-Language: en-us, en MIME-Version: 1.0 To: gentoo-portage-dev@lists.gentoo.org References: <200406291415.18659.george@gentoo.org> <200406302207.52557.pauldv@gentoo.org> <40F25500.103@wanadoo.fr> <42170.202.117.114.8.1089898236.squirrel@202.117.114.8> <40F7806F.4000200@wanadoo.fr> <45791.202.117.114.8.1089965420.squirrel@202.117.114.8> In-Reply-To: <45791.202.117.114.8.1089965420.squirrel@202.117.114.8> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new-20030616-p7 (Debian) at zeni.fr Subject: Re: [gentoo-portage-dev] Re: Re: portage-ng roadmap? X-Archives-Salt: e100a056-dc80-4bca-8f32-acd2f4517923 X-Archives-Hash: ead5f3e69bf2d5a918e15d8b82511a14 > You're right, they probably don't. My system will be quite modular and I image > a new tree, maybe I'll implement it in the initial release. One concept I'm > thinking about is something I call xpack (where xbuild is the extension of > ebuilds that should be guaranteed to work with the new parser). This basically > is a text based packaging format (like tar, but actually diffeable), that > would contain all parts needed for an ebuild (source is optional). Such a file > would make things a lot easier to manage and to download on demand. Totally agree. You can also force a validating commit with cvs : any commit would have to pass QA test (parsing) to be really commited. But, please consider not using rsync anymore. It's too slow for 85 000 files :( as previously discuss, subversion would be great. The best way is maybe the debian way : Put all xbuilds in a single tar file that would downloaded when "emerge update" (example). > While my main focus will not be on ondemand downloading of xpacks (ebuilds is > pointless) it should be fairly trivial to generate metadata files for the > packages contained, maybe even on a category level. The transfer size could > still be sizeable though. I believe that introduction of xpack files > containing everything needed for an ebuild (except the manifest and > metadata.xml) allready reduces the amount of files in the tree enormously. It > also helps in being able to easilly remove unused patches ;-). I like this new portage :) So these xbuilds are not needed on end-users computers. They are only needed to generate the dependance tree. If you need any help on this, please email me. Philippe -- gentoo-portage-dev@gentoo.org mailing list