| 1 |
Ühel kenal päeval, N, 26.01.2017 kell 22:33, kirjutas Mike Gilbert: |
| 2 |
> I recently ran into a REQUIRED_USE constraint that required I select |
| 3 |
> between berkdb and gdbm for an email client. |
| 4 |
|
| 5 |
There shouldn't be a REQUIRED_USE constraint that forces you to select |
| 6 |
one or the other. The maintainer should be giving the choice of both, |
| 7 |
but if only one can be chosen, the maintainer should make the choice |
| 8 |
for you by preferring one of them. Likely gdbm, given berkdb licensing |
| 9 |
saga. |
| 10 |
Though I guess this is a little bit more problematic when that DB is |
| 11 |
long living, but I think it should still work good enough with this |
| 12 |
guideline. |
| 13 |
|
| 14 |
Then there is no need to think about what is enabled globally or not. |
| 15 |
Point being, use REQUIRED_USE sparingly, and rarely a good idea to |
| 16 |
block things with common global USE flags, or demand a local USE flag |
| 17 |
based on a default enabled global USE flag without locally USE |
| 18 |
defaulting that global flag too - and other such cases. |
| 19 |
|
| 20 |
I'd talk to the maintainer(s) of such package(s) via bugzilla or other |
| 21 |
means and discuss such REQUIRED_USE potential overuse. |
| 22 |
|
| 23 |
> Looking through our profiles, I see we have both berkdb and gdbm |
| 24 |
> enabled "globally". |
| 25 |
> |
| 26 |
> default/linux/make.defaults:USE="berkdb crypt ipv6 ncurses nls pam |
| 27 |
> readline ssl tcpd zlib" |
| 28 |
> releases/make.defaults:USE="acl gdbm nptl unicode" |
| 29 |
> |
| 30 |
> Is there any reason to have these USE flags enabled globally? |
| 31 |
> |
| 32 |
> These USE seem pretty package-specific in scope. On my system, they |
| 33 |
> are used by around a dozen of 1000+ installed packages. I think it |
| 34 |
> might make sense to migrate them to appropriate IUSE defaults, or |
| 35 |
> leave them disabled where they do not provide critical functionality. |
Archives