Dnia 2013-06-01, o godz. 12:41:06 William Hubbs <[email protected]> napisał(a):
> On Thu, May 30, 2013 at 01:23:59PM +0200, Ralph Sennhauser wrote: > > William, each time this comes up you overred the _reasonably_. > > Controlling dependencies is always reasonable but beyond that it's case > > by case. Just because you can is never a valid reason. Often there are > > options you clearly only want to toggle if you are a developer or > > options meant for porting to alternative operating systems which lack > > some bells and whistles and the like. Another example is configuring a > > library for bundling with an app. The world is bigger than linux > > distros. > > Ralph, I never said anything about disagreeing with these cases. I'm > talking about purely optional features of packages which do not > have any bearing on runtime dependencies or cause breakage. > > If a configure script offers switches for purely optional features, we > should, imo, 1) give the users use flags to control these features or > 2)hard code the settings we want in our ebuilds. > > What do you think? That depends on a package and on the case. If a switch only changes the default in a config file, a flag is useless. If a switch toggles a feature that does not introduce additional dependencies, is small and can be toggled from within the app, a flag is useless. If a switch toggles a install of a tiny file which most people either want or don't care about, a flag is useless. -- Best regards, Michał Górny
signature.asc
Description: PGP signature
