| 1 |
On 02/03/2017 08:21 AM, Ian Stakenvicius wrote: |
| 2 |
>> |
| 3 |
>> How about rather changing our defaults to satisfy the minimalists who |
| 4 |
>> don't mind drastically reduced functionality and usability in pursuit |
| 5 |
>> of "minimalism" we just strive to make USE="-*" mostly usable, so the |
| 6 |
>> minimalists can get what they want, while still having sane defaults. |
| 7 |
>> |
| 8 |
> |
| 9 |
> I'm in favour of this too -- I know we don't "officially" support |
| 10 |
> USE="-*" but I think we should still strive to make it work with |
| 11 |
> minimal effort to end-users -- that effort being mainly setting |
| 12 |
> whatever is necessary for REQUIRED_USE resolution. |
| 13 |
> |
| 14 |
|
| 15 |
It will never be easy, because USE="-*" overrides your profile. What |
| 16 |
people want is a way to have USE="-*" apply between the base profile and |
| 17 |
the one that they select. |
| 18 |
|
| 19 |
This is all easily fixed by creating a new profile one-level above base |
| 20 |
where developers can put their favorite USE flags: |
| 21 |
|
| 22 |
1. We create a new empty profile called "penultimate" inheriting |
| 23 |
from base. |
| 24 |
|
| 25 |
2. Update the profiles that inherit from base to inherit from |
| 26 |
penultimate. |
| 27 |
|
| 28 |
3. Move every upstream and maintainer-pet IUSE default into the |
| 29 |
penultimate profile. |
| 30 |
|
| 31 |
4. Make it policy that IUSE defaults should only be used for |
| 32 |
critical flags and REQUIRED_USE persuasion. |
| 33 |
|
| 34 |
5. Now we can create embedded, hardened, etc. profiles that inherit |
| 35 |
from base and get a minimal working set of USE flags. |
Archives