From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 337 invoked from network); 11 Jun 2004 21:15:50 +0000 Received: from smtp.gentoo.org (156.56.111.197) by lists.gentoo.org with AES256-SHA encrypted SMTP; 11 Jun 2004 21:15:50 +0000 Received: from lists.gentoo.org ([156.56.111.196] helo=parrot.gentoo.org) by smtp.gentoo.org with esmtp (Exim 4.34) id 1BYtNL-00041v-Ow for arch-gentoo-portage-dev@lists.gentoo.org; Fri, 11 Jun 2004 21:15:48 +0000 Received: (qmail 3834 invoked by uid 89); 11 Jun 2004 21:15:46 +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 4449 invoked from network); 11 Jun 2004 21:15:46 +0000 Message-ID: <40CA20FD.8040907@wanadoo.fr> Date: Fri, 11 Jun 2004 23:15:41 +0200 From: =?ISO-8859-15?Q?Philippe_Lafoucri=E8re?= Reply-To: lafou@wanadoo.fr Organization: Zeni Corporation User-Agent: Mozilla Thunderbird 0.5 (X11/20040208) X-Accept-Language: en-us, en MIME-Version: 1.0 To: gentoo-portage-dev@lists.gentoo.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: [gentoo-portage-dev] portage doc & cache X-Archives-Salt: 29ac0cc8-ddc3-44d3-8511-f26545e06771 X-Archives-Hash: 0a38e5d6421bc99b9c4c7ceda4128a78 Hi all I'm wondering where I can find some doc about portage, and especially the cache part. I use debian at work, and get so sad when doing an emerge rsync at home (10 or 15 minutes to rsync, and almost 5 minutes to calculate world dependancies) on a bi-athlon 1.8GHz. I just wanted to check that the cache system is really a cache :) maybe ebuilds should be "compiled" into seriaziled objects or something similar. Only an emerge rsync (or something called "emerge update") would fetch new ebuilds, and compile new ones (we don't care anymore of hand modified files after sync). On the other hand, I was thinkink of the "rsync way" to synchronise the portage tree. Why don't we use a portage tree ID (incremented each time an ebuild is commited to CVS). For exemple, I have the tree number 12512. Current portage tree ID is 12514. I just need too fresh ebuilds. I don't think it would be really difficult to implement a server that would handle requests like : - "tell me which files where updated since 12512" - "files are : foo.ebuild bar.ebuild" [emerge is download foo.ebuild, bar.ebuild here] Moreover, do I REALLY need all ebuilds content ???? Why can't portage just look at some headers (with arch, desc, etc.) and left the install part on other files. Rsync local tree would be lighter, and faster to sync. When you need to emerge some program, emerge would download the _real_ ebuild file, the digests, the distfiles, etc. The headers can also be contained in one large tar.gz file, to reduce bandwith again (I know, like debian). I know this stuff might let you think I'm crazy to rebuild all portage, but here are some ideas to dig :D -- gentoo-portage-dev@gentoo.org mailing list