| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 26/07/14 04:05 AM, Duncan wrote: |
| 5 |
> Ian Stakenvicius posted on Fri, 25 Jul 2014 14:49:44 -0400 as |
| 6 |
> excerpted: |
| 7 |
> |
| 8 |
>> Hey all.. So, putting aside for now how much of a mess this |
| 9 |
>> would be to implement in the virtuals' ebuilds themselves, what |
| 10 |
>> do people think of changing the virtuals so that they contain an |
| 11 |
>> entry in IUSE for each provider that can satisfy it? |
| 12 |
>> |
| 13 |
>> The idea here is that the package satisfying a virtual could be |
| 14 |
>> optionally explicitly-chosen through package.use (or USE= in |
| 15 |
>> make.conf, perhaps) instead of having an entry in @world, that |
| 16 |
>> way if nothing depends on the virtual then it and the provider |
| 17 |
>> can be - --depclean'ed from the system. The idea is specifically |
| 18 |
>> NOT to have rdeps depend on these flags, that would undermine the |
| 19 |
>> whole purpose of the virtual; it would just be for end-users to |
| 20 |
>> set if they so chose. |
| 21 |
>> |
| 22 |
>> This may also help with getting portage to peg a virtual's |
| 23 |
>> provider to a specific package instead of constantly trying to |
| 24 |
>> switch from one to another, ie, how systemd kept getting pulled |
| 25 |
>> in, in relation to the upower virtual. |
| 26 |
> |
| 27 |
> What about handling each such virtual_USE as a USE_EXPAND? |
| 28 |
> VIRTUAL_* as reserved-namespace USE_EXPAND would give us full |
| 29 |
> backward compatibility along with an immediately identifiable |
| 30 |
> namespace and virtually (heh) no possibility of confusion with |
| 31 |
> other configuration. |
| 32 |
> |
| 33 |
> Continuing with the earlier virtual/krb5 example, we'd have |
| 34 |
> VIRTUAL_KRB5, with possible settings in make.conf of: |
| 35 |
> |
| 36 |
> VIRTUAL_KRB5=mit-krb5 VIRTUAL_KRB5=heimdal |
| 37 |
> |
| 38 |
> Virtually no possibility of confusion with normal USE flags, and |
| 39 |
> the matching virtual would be immediately identifiable, so no |
| 40 |
> possibility of getting confused on what it applies to, either. |
| 41 |
> |
| 42 |
|
| 43 |
|
| 44 |
*shrug*, sure.. effectively we just start using |
| 45 |
IUSE="virtual_krb5_mit-krb5" instead of "mit-krb5" but yes this would |
| 46 |
work too. |
| 47 |
|
| 48 |
|
| 49 |
-----BEGIN PGP SIGNATURE----- |
| 50 |
Version: GnuPG v2 |
| 51 |
|
| 52 |
iF4EAREIAAYFAlPTrbUACgkQ2ugaI38ACPAbcAD/VapV0WR+Z7aWcyHeehHzoHSw |
| 53 |
Qi8o+EDkQpakD3bVVtAA/0WSTPsPmVWHq3Fn0iITXbprHsKWMV+mXPN23nbpUdzf |
| 54 |
=aE4s |
| 55 |
-----END PGP SIGNATURE----- |
Archives