| 1 |
On Tue, Aug 15, 2017 at 6:25 AM, Kristian Fiskerstrand <k_f@g.o> wrote: |
| 2 |
> On 08/15/2017 02:21 PM, Rich Freeman wrote: |
| 3 |
>> For example, could you say that a client-only install that still |
| 4 |
>> installs the X11 components is "minimal?" |
| 5 |
> |
| 6 |
> Its somewhat context dependent, for an X application this doesn't |
| 7 |
> necessarily constitute additional dependencies for the system (think |
| 8 |
> desktop profile), whereby an application that is primarily used on |
| 9 |
> servers suddenly needing some graphics processing dragging it in is |
| 10 |
> likely wrong. |
| 11 |
> |
| 12 |
> That said, the use flag description isn't more detailed than "minimal - |
| 13 |
> Install a very minimal build (disables, for example, plugins, fonts, |
| 14 |
> most drivers, non-critical features)", so I'd say it is appropriate |
| 15 |
> |
| 16 |
|
| 17 |
I'm not actually sure what you're advocating here. |
| 18 |
|
| 19 |
My suggestion is to avoid minimal entirely, because for a package like |
| 20 |
this it is just going to be confusing because there are so many |
| 21 |
different optional features and disabling any of them could be |
| 22 |
situational. It is probably also worth nothing that minimal is itself |
| 23 |
a negative flag. I really question whether we ought to have it at |
| 24 |
all. |
| 25 |
|
| 26 |
If you're suggesting to use minimal for bacula, then what specifically |
| 27 |
should it actually enable/disable in this particular case? |
| 28 |
|
| 29 |
For reference, the current IUSE is: |
| 30 |
IUSE="acl bacula-clientonly bacula-nodir bacula-nosd examples ipv6 |
| 31 |
libressl logwatch mysql postgres qt4 readline +sqlite ssl static tcpd |
| 32 |
vim-syntax X" |
| 33 |
|
| 34 |
There are a lot of features one might debate toggling with "minimal" |
| 35 |
in that list. |
| 36 |
|
| 37 |
-- |
| 38 |
Rich |
Archives