From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Ln5fm-0004Bp-8b for garchives@archives.gentoo.org; Fri, 27 Mar 2009 06:36:10 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 09548E0249; Fri, 27 Mar 2009 06:36:09 +0000 (UTC) Received: from sauxb.salomon.at (smtp.salomon.at [193.186.16.13]) by pigeon.gentoo.org (Postfix) with ESMTP id A29B0E0249 for ; Fri, 27 Mar 2009 06:36:08 +0000 (UTC) Received: from servex01.wamas.com (servex01.salomon.at [172.28.2.2]) by sauxb.salomon.at (8.12.10/8.12.10) with ESMTP id n2R6ZfCe022976 for ; Fri, 27 Mar 2009 07:35:41 +0100 (MET) Received: from [172.28.8.14] ([172.28.8.14]) by servex01.wamas.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 27 Mar 2009 07:35:41 +0100 Subject: Re: [gentoo-portage-dev] prefix portage chaining From: Markus Duft To: gentoo-portage-dev@lists.gentoo.org In-Reply-To: <1238087295.16056.9.camel@hangover> References: <000001c9a947$8acf66b0$a06e3410$@org> <20090325110015.GH12431@gentoo.org> <1237986877.28894.18.camel@localhost> <1238006668.11833.21.camel@hangover> <1238052368.6046.14.camel@localhost> <1238087295.16056.9.camel@hangover> Content-Type: text/plain Date: Fri, 27 Mar 2009 07:34:49 +0100 Message-Id: <1238135689.591.2.camel@localhost> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-portage-dev@lists.gentoo.org Reply-to: gentoo-portage-dev@lists.gentoo.org Mime-Version: 1.0 X-Mailer: Evolution 2.24.5 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 27 Mar 2009 06:35:41.0042 (UTC) FILETIME=[3F878520:01C9AEA6] X-Spam-Info: -1.946 () ALL_TRUSTED,AWL,BAYES_50 X-Scanned-By: MIMEDefang 2.54 on 172.28.2.13 X-Archives-Salt: b3ccbe68-9996-459f-940f-1cb1e5c50e31 X-Archives-Hash: ebdb6ac7173e52829dc70c7ddb297cdb On Thu, 2009-03-26 at 10:08 -0700, Ned Ludd wrote: > On Thu, 2009-03-26 at 08:26 +0100, Markus Duft wrote: > > On Wed, 2009-03-25 at 11:44 -0700, Ned Ludd wrote: > > [snip] > > > > > > > > > While much of what you are talking about here mainly applies to prefix, > > > it looks to me from glancing over the code that you might of solved a > > > long standing problem in the embedded world with cross compiling via > > > portage. 222895 If that is the case, then I owe you a beer. one about > > > the size of a keg. > > > > > > > lol, thx for the beer ;) > > > > hmm... looking over that patch again, the only EPREFIX dependent thing > > is, that i'm removing EPREFIX from the vartree class again :) so this > > should pretty much plain apply to main too, and simply work. you may > > want to rename READONLY_EPREFIX to READONLY_ROOT, but thats it :) > > > > the other stuff besides portage modification (baselayout patchery, etc. > > is prefix specific again, so all you'd need is the portage changes. > > > > if you will try it, please let me know if it worked :) with the attached > > patch "sed -i -e 's,READONLY_EPREFIX,READONLY_ROOT,g'", and applying to > > an installed /usr/lib/portage should enable you to do it. > > (backup /usr/lib/portage - i trust my work, but... we never know for > > sure :)) > > > > then add to make.conf: READONLY_ROOT=/my/other/root:DEPEND > > > > i hope this is what you where looking for...! and i hope it doesn't > > somehow clash with the existing cross compile logic in portage regarding > > where to merge to... > > > > Cheers, Markus > > > patch failed a few hunks for me on ~arch vanilla-portage. I did point > out the patch to one of the gentoo embedded/openmoko guys. Think they > will be the most eager to test this. > > In our case if the code did work out whatever you call READONLY_ROOT we > would probably need to expand to allow for more that one ROOT if it has > to be defined in the parent /etc/make.conf not the parent one, but the "childs" one. so you'd say READONLY_ROOT="/:DEPEND" in your $ROOT. so when merging to $ROOT, '/' will be searched for DEPENDs. er... you can remove all hunks for vartree.py and remove the argument "kill_eprefix" from all calls to vartree (should be one only i guess). sorry - forgot about that. Cheers, Markus > >