| 1 |
On Tue, 28 May 2013 17:15:40 -0500 |
| 2 |
William Hubbs <williamh@g.o> wrote: |
| 3 |
|
| 4 |
> On Tue, May 28, 2013 at 09:07:37PM +0200, Michał Górny wrote: |
| 5 |
> > For the others, how large is the benefit of having them switchable? |
| 6 |
> > At least some of them look like something that wouldn't hurt people |
| 7 |
> > if it was always-built. |
| 8 |
> |
| 9 |
> The dev manual states that use flags are to control optional |
| 10 |
> dependencies and _settings_ which a user may reasonably want to select |
| 11 |
> [1]. |
| 12 |
|
| 13 |
William, each time this comes up you overred the _reasonably_. |
| 14 |
Controlling dependencies is always reasonable but beyond that it's case |
| 15 |
by case. Just because you can is never a valid reason. Often there are |
| 16 |
options you clearly only want to toggle if you are a developer or |
| 17 |
options meant for porting to alternative operating systems which lack |
| 18 |
some bells and whistles and the like. Another example is configuring a |
| 19 |
library for bundling with an app. The world is bigger than linux |
| 20 |
distros. |
| 21 |
|
| 22 |
> Since the developer gives us the ability to control this with |
| 23 |
> configure switches, I feel pretty strongly that we should give the |
| 24 |
> user that control. |
| 25 |
|
| 26 |
Useless options within the given context are an usability issue and |
| 27 |
those who want to toggle stuff for it's own sake still have EXTRA_ECONF. |
| 28 |
|
| 29 |
Ralph |
| 30 |
|
| 31 |
> |
| 32 |
> William |
| 33 |
> |
| 34 |
> [1] http://devmanual.gentoo.org/general-concepts/use-flags/index.html |
Archives