| 1 |
On 02/19/2013 07:21 AM, Brian Dolbec wrote: |
| 2 |
> On Tue, 2013-02-19 at 14:10 +0100, Thomas Kahle wrote: |
| 3 |
>> ... if it is used in the ebuild? |
| 4 |
>> |
| 5 |
>> It is a system package here on amd64, but is it everywhere? |
| 6 |
>> |
| 7 |
>> Cheers, |
| 8 |
>> Thomas |
| 9 |
>> |
| 10 |
> |
| 11 |
> Only if the pkg is also a system package. I recently ran into a problem |
| 12 |
> running a catalyst build because portage-utils did not list the xz-utils |
| 13 |
> dep which was another system package. It failed to unpack because |
| 14 |
> xz-utils was still waiting to be merged. I was running catalyst with |
| 15 |
> --jobs=3. |
| 16 |
|
| 17 |
If it's not in $PORTDIR/profiles/default/linux/packages.build then it's |
| 18 |
not necessarily included in stage1 and therefore you can't rely on it |
| 19 |
for stage1 -> stage2 -> stage3. If that's the case, then it has to be in |
| 20 |
*DEPEND for anything in stage3. |
| 21 |
-- |
| 22 |
Thanks, |
| 23 |
Zac |
Archives