| 1 |
On Fri, 3 Feb 2017 19:59:34 -0500 |
| 2 |
Ian Stakenvicius <axs@g.o> wrote: |
| 3 |
|
| 4 |
> On 03/02/17 02:37 PM, Michael Orlitzky wrote: |
| 5 |
> > On 02/03/2017 10:30 AM, Ian Stakenvicius wrote: |
| 6 |
> >> |
| 7 |
> >> ok you lost me. Could you provide an explicit example of what you |
| 8 |
> >> would want to see enabled in the profile (while everything else is |
| 9 |
> >> disabled) that you don't get when USE="-*" is set? |
| 10 |
> > |
| 11 |
> > USE="hardened pax_kernel ..." |
| 12 |
> > |
| 13 |
> |
| 14 |
> ok, so global flags that are never modified via IUSE defaults. It |
| 15 |
> still looks to me like all you need to do to get what you want is swap |
| 16 |
> the order of 'conf' and 'defaults' in USE_ORDER? (man make.conf) |
| 17 |
> |
| 18 |
> > |
| 19 |
> > I don't want to turn off all IUSE defaults. Since we have no policy |
| 20 |
> > on what IUSE defaults should be used for, half of them are |
| 21 |
> > important, and the other half are junk. I don't want to disable the |
| 22 |
> > ones that are critical for the package to function, and I don't |
| 23 |
> > want to disable the ones that satisfy an (otherwise unsatisfied) |
| 24 |
> > REQUIRED_USE constraint. |
| 25 |
> |
| 26 |
> And herein lies the crux. "Junk" is your definition, but it's not |
| 27 |
> necessarily the maintainer's definition. "Critical for the package to |
| 28 |
> function" is entirely dependent on what you expect to use the package |
| 29 |
> for. If you want to disable everything optional then USE="-*" will do |
| 30 |
> that, and really all you should be losing is the ability to have |
| 31 |
> REQUIRED_USE auto-resolve based on the IUSE defaults that are set. |
| 32 |
> However, even in that case, it seems likely that you may well want to |
| 33 |
> use a different option to resolve a REQUIRED_USE conflict to ensure |
| 34 |
> your minimalist install than is the default that the maintainer |
| 35 |
> provided. |
| 36 |
> |
| 37 |
|
| 38 |
I think the current policy of "maintainer's discretion" is probably the |
| 39 |
only reasonable way to approach IUSE defaults. Attempting to dictate |
| 40 |
some policy based on differing definitions of what is acceptable or not |
| 41 |
is just a path to a lot of pain for very little gain. I don't think |
| 42 |
that there are a very large proportion of people who want some sort of |
| 43 |
"minimal" system, sacrificing basic, expected functionality (as say |
| 44 |
"-readline" on app-shells/bash would do) in the default configuration |
| 45 |
. |
| 46 |
Leaving the IUSE defaults up to the maintainer allows said maintainer |
| 47 |
to select what they consider reasonable defaults. |
Archives