1 |
On Fri, Jan 27, 2017 at 06:27:09PM +0200, Mart Raudsepp wrote: |
2 |
> Ühel kenal päeval, R, 27.01.2017 kell 13:08, kirjutas Kristian |
3 |
> Fiskerstrand: |
4 |
> > On 01/27/2017 01:01 PM, Dirkjan Ochtman wrote: |
5 |
> > > On Fri, Jan 27, 2017 at 8:54 AM, Mart Raudsepp <leio@g.o> |
6 |
> > > wrote: |
7 |
> > > > Ühel kenal päeval, N, 26.01.2017 kell 22:33, kirjutas Mike |
8 |
> > > > Gilbert: |
9 |
> > > > > I recently ran into a REQUIRED_USE constraint that required I |
10 |
> > > > > select |
11 |
> > > > > between berkdb and gdbm for an email client. |
12 |
> > > > |
13 |
> > > > There shouldn't be a REQUIRED_USE constraint that forces you to |
14 |
> > > > select |
15 |
> > > > one or the other. The maintainer should be giving the choice of |
16 |
> > > > both, |
17 |
> > > > but if only one can be chosen, the maintainer should make the |
18 |
> > > > choice |
19 |
> > > > for you by preferring one of them. Likely gdbm, given berkdb |
20 |
> > > > licensing |
21 |
> > > > saga. |
22 |
> > > |
23 |
> > > I'm not sure this makes sense to me. If the package will actually |
24 |
> > > select one implementation out of a set, it makes sense to me that |
25 |
> > > the |
26 |
> > > maintainer for that package makes that choice explicit towards the |
27 |
> > > user. In that case, setting REQUIRED_USE accordingly seems exactly |
28 |
> > > right. The maintainer should set a good default, but if the user's |
29 |
> > > USE |
30 |
> > > settings are inconclusive in getting to the choice of |
31 |
> > > implementation, |
32 |
> > > it's better to whine explicitly than try to guess implicitly what |
33 |
> > > the |
34 |
> > > user wanted. |
35 |
> > |
36 |
> > I tend to agree with this sentiment, explicit over implicit behavior |
37 |
> > ensures better debugging ability and security considerations. |
38 |
|
39 |
I agree, I prefer explicit strongly over implicit. |
40 |
|
41 |
> It breaks the highly sought after "Gentoo is about choice" mantra. |
42 |
> In this case, choice to not care and have the best chosen for me. |
43 |
|
44 |
Actually it doesn't. In this case the user should make a choice rather |
45 |
than the maintainer silently making a choice behind their back. |
46 |
|
47 |
William |