Archives
Archives
| From: | Ian Stakenvicius <axs@g.o> | ||
|---|---|---|---|
| To: | gentoo-dev@l.g.o | ||
| Subject: | Re: [gentoo-dev] Guidelines for IUSE defaults | ||
| Date: | Thu, 02 Feb 2017 14:56:51 | ||
| Message-Id: | EF72D3B2-2032-4943-96CB-30D8D2E665F1@gentoo.org | ||
| In Reply to: | [gentoo-dev] Guidelines for IUSE defaults by Michael Orlitzky |
||
| 1 | > On Feb 2, 2017, at 9:11 AM, Michael Orlitzky <mjo@g.o> wrote: |
| 2 | > |
| 3 | > IUSE defaults are used in a few different ways: |
| 4 | > |
| 5 | > 1 To ensure that critical functionality is enabled. |
| 6 | > |
| 7 | > * Example: force the "unix" module for apache. |
| 8 | > |
| 9 | |
| 10 | This is not what IUSE defaults are for, this should be done with package.use{,.stable}.{mask,force} in profiles. If functionality is critical then there (A) shouldn't be a use flag, or (B) shouldn't be a way for USE= in make.conf to disable it. |
| Subject | Author |
|---|---|
| Re: [gentoo-dev] Guidelines for IUSE defaults | Michael Orlitzky <mjo@g.o> |