Re: [gentoo-portage-dev] repos.conf location w.r.t PORTAGE_CONFIGROOT

[Zac Medico]

On 05/06/15 15:09, Joakim Tjernlund wrote:
> On Wed, 2015-05-06 at 21:57 +0000, Joakim Tjernlund wrote:
>> On Wed, 2015-05-06 at 14:36 -0700, Zac Medico wrote:
>>> On 05/06/15 14:30, Joakim Tjernlund wrote:
>>>> 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 problems.
>>>>>>>>>>> I cannot make emerge to select my old ebuilds in an overlay over those
>>>>>>>>>>> in /usr/portage.
>>>>>>>>>>>
>>>>>>>>>>> What new is since last time I did this is /etc/portage/repos.conf/
>>>>>>>>>>> I suspect emerge always reads /etc/portage/repos.conf/ no matter
>>>>>>>>>>> what I set PORTAGE_CONFIGROOT / ROOT to ?
>>>>>>>>>>>
>>>>>>>>>>>  Jocke
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> It instantiates 2 config instances, one using /etc/portage/repos.conf
>>>>>>>>>> (for build time DEPEND) and another one using
>>>>>>>>>> $PORTAGE_CONFIGROOT/etc/portage/repos.conf (for run time {P,R}DEPEND).
>>>>>>>>>> You can see that it's joined with PORTAGE_CONFIGROOT in the
>>>>>>>>>> load_repository_config function:
>>>>>>>>>>
>>>>>>>>>> https://gitweb.gentoo.org/proj/portage.git/tree/pym/portage/repository/config.py?id=0f191113
>>>>>>>>>> cc
>>>>>>>>>> cd04
>>>>>>>>>> 9e11
>>>>>>>>>> fdbe
>>>>>>>>>> 73
>>>>>>>>>> 493eb1efbf4bf89e#n971
>>>>>>>>>
>>>>>>>>> I see, doesn't this prevent exactly what I want to do?
>>>>>>>>>
>>>>>>>>> I can't see why this should be needed, it only creates a mess, another example:
>>>>>>>>> I tried to specify exact version of my old binutils and while that worked, portage wanted
>>>>>>>>> to pull in a newer binutils-config from the hosts master gentoo repo and
>>>>>>>>> thus the build failed.
>>>>>>>>>
>>>>>>>>> If a someone really wants this behaviour, he can just add the hosts master repo
>>>>>>>>> in his PORTAGE_CONFIGROOT IMHO
>>>>>>>>>
>>>>>>>
>>>>>>> Maybe emerge --root-deps=rdeps is what you are looking for. This will
>>>>>>> cause it to ignore DEPEND.
>>>>>>
>>>>>> 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.
>>>>>>
>>>>>> I realize now that I can change what repos are searched by using
>>>>>> PORTAGE_REPOSITORIES=/my/own/repos.conf/
>>>>>> but I still find the default behaviour very confusing and I don't see that it is useful.
>>>>>
>>>>> 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=/, then it's supposed to use the repositories configured for ROOT=/.
>>>>
>>>> I see, but in my case I only install into my sysroot so I don't want this behaviour.
>>>
>>> So, why don't you use the --root-deps option?
>>
>> Just did(and --root-deps=rdeps too) and it didn't work, still wants to use
>> my newer hosts pkgs. :(
>>
>>>
>>>> Can you not add a test for CHOST/CBULID/CTARGET (never remeber which is which) so portage
>>>> only adds the hosts repo if they are the same?
>>>> Basically only add the master repo if not cross-building?
>>>
>>> It would have to be tied to an option like --root-deps. I still suspect
>>> that --root-deps is what you really want.
>>
>> No, I really think that portage is over doing things here.
>> Anyone that is using ROOT and PORTAGE_CONFIGROOT only needs the main repo iff
>>
>
> hmm, is ROOT and PORTAGE_CONFIGROOT really useful for non cross builds?

They are only for cross builds. What else would you use them for?

> Installing DEPEND
> into host require you use the same conf as the host(USE mainly I guess)?

No, they have separate configurations.
-- 
Thanks,
Zac