| 1 |
On 05/06/15 14:30, Joakim Tjernlund wrote: |
| 2 |
> On Wed, 2015-05-06 at 13:30 -0700, Zac Medico wrote: |
| 3 |
>> On 05/06/15 13:22, Joakim Tjernlund wrote: |
| 4 |
>>> On Wed, 2015-05-06 at 12:54 -0700, Zac Medico wrote: |
| 5 |
>>>> On 05/06/15 12:41, Joakim Tjernlund wrote: |
| 6 |
>>>>> On Wed, 2015-05-06 at 19:13 +0000, Joakim Tjernlund wrote: |
| 7 |
>>>>>> On Wed, 2015-05-06 at 11:37 -0700, Zac Medico wrote: |
| 8 |
>>>>>>> On 05/06/15 09:54, Joakim Tjernlund wrote: |
| 9 |
>>>>>>>> I am trying to rebuild an old cross sysroot and I got problems. |
| 10 |
>>>>>>>> I cannot make emerge to select my old ebuilds in an overlay over those |
| 11 |
>>>>>>>> in /usr/portage. |
| 12 |
>>>>>>>> |
| 13 |
>>>>>>>> What new is since last time I did this is /etc/portage/repos.conf/ |
| 14 |
>>>>>>>> I suspect emerge always reads /etc/portage/repos.conf/ no matter |
| 15 |
>>>>>>>> what I set PORTAGE_CONFIGROOT / ROOT to ? |
| 16 |
>>>>>>>> |
| 17 |
>>>>>>>> Jocke |
| 18 |
>>>>>>>> |
| 19 |
>>>>>>> |
| 20 |
>>>>>>> It instantiates 2 config instances, one using /etc/portage/repos.conf |
| 21 |
>>>>>>> (for build time DEPEND) and another one using |
| 22 |
>>>>>>> $PORTAGE_CONFIGROOT/etc/portage/repos.conf (for run time {P,R}DEPEND). |
| 23 |
>>>>>>> You can see that it's joined with PORTAGE_CONFIGROOT in the |
| 24 |
>>>>>>> load_repository_config function: |
| 25 |
>>>>>>> |
| 26 |
>>>>>>> https://gitweb.gentoo.org/proj/portage.git/tree/pym/portage/repository/config.py?id=0f191113cccd04 |
| 27 |
>>>>>>> 9e11 |
| 28 |
>>>>>>> fdbe |
| 29 |
>>>>>>> 73 |
| 30 |
>>>>>>> 493eb1efbf4bf89e#n971 |
| 31 |
>>>>>> |
| 32 |
>>>>>> I see, doesn't this prevent exactly what I want to do? |
| 33 |
>>>>>> |
| 34 |
>>>>>> I can't see why this should be needed, it only creates a mess, another example: |
| 35 |
>>>>>> I tried to specify exact version of my old binutils and while that worked, portage wanted |
| 36 |
>>>>>> to pull in a newer binutils-config from the hosts master gentoo repo and |
| 37 |
>>>>>> thus the build failed. |
| 38 |
>>>>>> |
| 39 |
>>>>>> If a someone really wants this behaviour, he can just add the hosts master repo |
| 40 |
>>>>>> in his PORTAGE_CONFIGROOT IMHO |
| 41 |
>>>>>> |
| 42 |
>>>> |
| 43 |
>>>> Maybe emerge --root-deps=rdeps is what you are looking for. This will |
| 44 |
>>>> cause it to ignore DEPEND. |
| 45 |
>>> |
| 46 |
>>> That is not the same is it? if I "emerge ncurses" it will build ncurses but still |
| 47 |
>>> take the ebuild from the hosts master since it is newer version. |
| 48 |
>>> |
| 49 |
>>> I realize now that I can change what repos are searched by using PORTAGE_REPOSITORIES=/my/own/repos.conf/ |
| 50 |
>>> but I still find the default behaviour very confusing and I don't see that it is useful. |
| 51 |
>> |
| 52 |
>> The idea is that you have separate repositories configured for each |
| 53 |
>> ROOT. If it's satisfying a build-time DEPEND that will be installed into |
| 54 |
>> ROOT=/, then it's supposed to use the repositories configured for ROOT=/. |
| 55 |
> |
| 56 |
> I see, but in my case I only install into my sysroot so I don't want this behaviour. |
| 57 |
|
| 58 |
So, why don't you use the --root-deps option? |
| 59 |
|
| 60 |
> Can you not add a test for CHOST/CBULID/CTARGET (never remeber which is which) so portage |
| 61 |
> only adds the hosts repo if they are the same? |
| 62 |
> Basically only add the master repo if not cross-building? |
| 63 |
|
| 64 |
It would have to be tied to an option like --root-deps. I still suspect |
| 65 |
that --root-deps is what you really want. |
| 66 |
-- |
| 67 |
Thanks, |
| 68 |
Zac |
Archives