| 1 |
On 11/29/2011 08:51 PM, Duncan wrote: |
| 2 |
> Zac Medico posted on Tue, 29 Nov 2011 18:29:20 -0800 as excerpted: |
| 3 |
> |
| 4 |
>> One nice thing about removing them from the system profile is that it |
| 5 |
>> allows for greater parallelization with emerge --jobs, since packages |
| 6 |
>> that's aren't in the system set don't trigger the code for bug 256616 |
| 7 |
>> [1] which limits parallelization as a safety precaution. |
| 8 |
>> |
| 9 |
>> [1] https://bugs.gentoo.org/show_bug.cgi?id=256616 |
| 10 |
> |
| 11 |
> And a VERY nice benefit that is, too. =:^) |
| 12 |
> |
| 13 |
> Except, don't dependencies of system profile packages get the same safety |
| 14 |
> precaution applied, and at the level we're talking here, zlib, etc, |
| 15 |
> aren't such packages going to almost certainly be dependencies of @system |
| 16 |
> on a normal system, even if they're not in @system itself? |
| 17 |
> |
| 18 |
> If so, that's a relatively limited benefit in most cases. |
| 19 |
|
| 20 |
Well, maybe there's not much parallelization benefit for sys-libs/zlib. |
| 21 |
If it wasn't for implicit system dependencies, the system set and its |
| 22 |
dependencies wouldn't need this kind of special treatment. |
| 23 |
-- |
| 24 |
Thanks, |
| 25 |
Zac |
Archives