public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New USE_EXPAND flag for www-servers/monkeyd
Date: Sat, 1 Jun 2013 12:41:06 -0500	[thread overview]
Message-ID: <20130601174106.GA20043@linux1> (raw)
In-Reply-To: <20130530132359.04cf5815@sera-20.lan>

[-- Attachment #1: Type: text/plain, Size: 1507 bytes --]

On Thu, May 30, 2013 at 01:23:59PM +0200, Ralph Sennhauser wrote:
> On Tue, 28 May 2013 17:15:40 -0500
> William Hubbs <williamh@gentoo.org> wrote:
> 
> > On Tue, May 28, 2013 at 09:07:37PM +0200, Michał Górny wrote:
> > > For the others, how large is the benefit of having them switchable?
> > > At least some of them look like something that wouldn't hurt people
> > > if it was always-built.
> > 
> > The dev manual states that use flags are to control optional
> > dependencies and _settings_ which a user may reasonably want to select
> > [1].
>  
> 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?

William


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2013-06-01 17:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-27 20:38 [gentoo-dev] New USE_EXPAND flag for www-servers/monkeyd Anthony G. Basile
2013-05-28  6:01 ` Tony "Chainsaw" Vroon
2013-05-28 11:30   ` Anthony G. Basile
2013-05-28  6:24 ` René Neumann
2013-05-28 15:35 ` Michał Górny
2013-05-28 18:57   ` Anthony G. Basile
2013-05-28 19:07     ` Michał Górny
2013-05-28 19:22       ` Anthony G. Basile
2013-05-28 20:18         ` Michał Górny
2013-05-31 13:23           ` Gilles Dartiguelongue
2013-05-28 22:15       ` William Hubbs
2013-05-30 11:23         ` Ralph Sennhauser
2013-06-01 17:41           ` William Hubbs [this message]
2013-06-01 18:00             ` Michał Górny
2013-06-01 20:20               ` William Hubbs
2013-06-01 20:26                 ` Michał Górny
2013-06-02  0:21                   ` William Hubbs

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130601174106.GA20043@linux1 \
    --to=williamh@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox