| 1 |
Jason Stubbs wrote: |
| 2 |
|
| 3 |
>On Monday 20 June 2005 01:48, Alin Nastac wrote: |
| 4 |
> |
| 5 |
> |
| 6 |
>>net-dialup/pppconfig-2.3.11-r1 depends on LINGUAS, but the list of |
| 7 |
>>supported languages is created in pkg_unpack, based on what tarball |
| 8 |
>>contains. |
| 9 |
>> |
| 10 |
>> |
| 11 |
> |
| 12 |
>What happened to determinism and predictability? From the user's standpoint, |
| 13 |
>there is no way to know what is going to be installed until it is actually |
| 14 |
>installed. |
| 15 |
> |
| 16 |
> |
| 17 |
> |
| 18 |
I don't really understand why you consider pppconfig unpredictable. |
| 19 |
the ebuild displays what languages will be installed. |
| 20 |
|
| 21 |
>>The IUSE thing would raise 2 problems: |
| 22 |
>> - lower maintainability - not really a major problem |
| 23 |
>> - if user wants all languages, it will be forced to select them one by |
| 24 |
>>one - now if LINGUAS is empty, all available languages gets installed. |
| 25 |
>> |
| 26 |
>> |
| 27 |
> |
| 28 |
>FRITZCAPI_CARDS FCDSL_CARDS VIDEO_CARDS INPUT_DEVICES LINGUAS |
| 29 |
> |
| 30 |
>Do any of these not follow the same pattern of empty var == all installed? Any |
| 31 |
>objections to making that a requirement for adding a new USE_EXPAND variable? |
| 32 |
>If so, the emerge *display* issue would be no problem. |
| 33 |
> |
| 34 |
> |
| 35 |
This would be fine as long as LINGUAS do not appear in IUSE. When |
| 36 |
LINGUAS var is empty, the "equery uses" report would be an abomination . |
Archives