| 1 |
On 12/11/2014 12:25 AM, Michał Górny wrote: |
| 2 |
> Dnia 2014-12-10, o godz. 18:08:00 |
| 3 |
> Zac Medico <zmedico@g.o> napisał(a): |
| 4 |
> |
| 5 |
>> Add support for a new @profile set which allows the profile to pull |
| 6 |
>> in additional packages that do not belong to the @system set. |
| 7 |
>> |
| 8 |
>> The motivation to have @profile separate from @system is that |
| 9 |
>> @system packages may have incomplete dependency specifications |
| 10 |
>> (due to long-standing Gentoo policy), and incomplete dependency |
| 11 |
>> specifications have deleterious effects on the ability of emerge |
| 12 |
>> --jobs to parallelize builds. So, unlike @system, packages added to |
| 13 |
>> @profile do not hurt emerge --jobs parallelization. |
| 14 |
>> |
| 15 |
>> Packages are added to the @profile set in the same way that they are |
| 16 |
>> added to the @system set, except that atoms in the @profile set are |
| 17 |
>> not preceded with a '*' character. Also, the @profile package set |
| 18 |
>> is only supported when 'profile-set' is listed in the layout.conf |
| 19 |
>> profile-formats field of the containing repository. |
| 20 |
> |
| 21 |
> PMS says PMs ought to ignore atoms without '*'. This means we can't use |
| 22 |
> it without profile EAPI change, or other PMs will start losing packages. |
| 23 |
|
| 24 |
It's hidden behind a layout.conf profile-formats flag, so it's beyond |
| 25 |
the scope of PMS. Package managers should reject the profile if they |
| 26 |
don't recognize the profile-formats flags that it declares. |
| 27 |
-- |
| 28 |
Thanks, |
| 29 |
Zac |
Archives