From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 522F3138CCC for ; Wed, 6 May 2015 21:30:29 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4101EE08A5; Wed, 6 May 2015 21:30:28 +0000 (UTC) Received: from smtp.transmode.se (smtp.transmode.se [31.15.61.139]) by pigeon.gentoo.org (Postfix) with ESMTP id 92877E08A0 for ; Wed, 6 May 2015 21:30:27 +0000 (UTC) Received: from exch2.transmode.se (exch2.transmode.se [192.168.203.24]) by smtp.transmode.se (Postfix) with ESMTP id 8BC011186FEA for ; Wed, 6 May 2015 23:30:26 +0200 (CEST) Received: from exch1.transmode.se (192.168.201.16) by exch2.transmode.se (192.168.203.24) with Microsoft SMTP Server (TLS) id 15.0.1076.9; Wed, 6 May 2015 23:30:26 +0200 Received: from exch1.transmode.se ([fe80::90bf:2c1d:c76a:2a46]) by exch1.transmode.se ([fe80::90bf:2c1d:c76a:2a46%17]) with mapi id 15.00.1076.000; Wed, 6 May 2015 23:30:25 +0200 From: Joakim Tjernlund To: "gentoo-portage-dev@lists.gentoo.org" Subject: Re: [gentoo-portage-dev] repos.conf location w.r.t PORTAGE_CONFIGROOT Thread-Topic: [gentoo-portage-dev] repos.conf location w.r.t PORTAGE_CONFIGROOT Thread-Index: AQHQiB1QmUc5Ht0PW0usjHjr9gcnAZ1vJayAgAAKIwCAAAfPgIAAA6SAgAAHxACAAAIegIAAENSA Date: Wed, 6 May 2015 21:30:24 +0000 Message-ID: <1430947825.27859.135.camel@transmode.se> References: <1430931268.27859.102.camel@transmode.se> <554A5F6D.5030807@gentoo.org> <1430939630.27859.113.camel@transmode.se> <1430941307.27859.116.camel@transmode.se> <554A7189.30503@gentoo.org> <1430943756.27859.126.camel@transmode.se> <554A79D3.1040001@gentoo.org> In-Reply-To: <554A79D3.1040001@gentoo.org> Accept-Language: en-US, sv-SE Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-mailer: Evolution 3.17.1 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [192.168.200.4] Content-Type: text/plain; charset="iso-8859-15" Content-ID: Content-Transfer-Encoding: quoted-printable 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-Archives-Salt: 19fef00a-4695-4676-ae3b-6159b14c0709 X-Archives-Hash: b61e900e4c18ce1a9877f0047371e163 On Wed, 2015-05-06 at 13:30 -0700, Zac Medico wrote: > On 05/06/15 13:22, Joakim Tjernlund wrote: > > On Wed, 2015-05-06 at 12:54 -0700, Zac Medico wrote: > > > On 05/06/15 12:41, Joakim Tjernlund wrote: > > > > On Wed, 2015-05-06 at 19:13 +0000, Joakim Tjernlund wrote: > > > > > On Wed, 2015-05-06 at 11:37 -0700, Zac Medico wrote: > > > > > > On 05/06/15 09:54, Joakim Tjernlund wrote: > > > > > > > I am trying to rebuild an old cross sysroot and I got problem= s. > > > > > > > I cannot make emerge to select my old ebuilds in an overlay o= ver those > > > > > > > in /usr/portage. > > > > > > >=20 > > > > > > > What new is since last time I did this is /etc/portage/repos.= conf/ > > > > > > > I suspect emerge always reads /etc/portage/repos.conf/ no mat= ter > > > > > > > what I set PORTAGE_CONFIGROOT / ROOT to ? > > > > > > >=20 > > > > > > > Jocke > > > > > > >=20 > > > > > >=20 > > > > > > It instantiates 2 config instances, one using /etc/portage/repo= s.conf > > > > > > (for build time DEPEND) and another one using > > > > > > $PORTAGE_CONFIGROOT/etc/portage/repos.conf (for run time {P,R}D= EPEND). > > > > > > You can see that it's joined with PORTAGE_CONFIGROOT in the > > > > > > load_repository_config function: > > > > > >=20 > > > > > > https://gitweb.gentoo.org/proj/portage.git/tree/pym/portage/rep= ository/config.py?id=3D0f191113cccd04 > > > > > > 9e11 > > > > > > fdbe > > > > > > 73 > > > > > > 493eb1efbf4bf89e#n971 > > > > >=20 > > > > > I see, doesn't this prevent exactly what I want to do? > > > > >=20 > > > > > I can't see why this should be needed, it only creates a mess, an= other example: > > > > > I tried to specify exact version of my old binutils and while tha= t worked, portage wanted > > > > > to pull in a newer binutils-config from the hosts master gentoo r= epo and > > > > > thus the build failed. > > > > >=20 > > > > > If a someone really wants this behaviour, he can just add the hos= ts master repo > > > > > in his PORTAGE_CONFIGROOT IMHO > > > > >=20 > > >=20 > > > Maybe emerge --root-deps=3Drdeps is what you are looking for. This wi= ll > > > cause it to ignore DEPEND. > >=20 > > That is not the same is it? if I "emerge ncurses" it will build ncurses= but still > > take the ebuild from the hosts master since it is newer version. > >=20 > > I realize now that I can change what repos are searched by using PORTAG= E_REPOSITORIES=3D/my/own/repos.conf/ > > but I still find the default behaviour very confusing and I don't see t= hat it is useful. >=20 > The idea is that you have separate repositories configured for each > ROOT. If it's satisfying a build-time DEPEND that will be installed into > ROOT=3D/, then it's supposed to use the repositories configured for ROOT= =3D/. I see, but in my case I only install into my sysroot so I don't want this b= ehaviour. Can you not add a test for CHOST/CBULID/CTARGET (never remeber which is whi= ch) so portage only adds the hosts repo if they are the same? Basically only add the master repo if not cross-building? Jocke=20