public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: new global use flag and a new category
Date: Mon, 30 Aug 2004 01:51:20 -0700	[thread overview]
Message-ID: <pan.2004.08.30.08.51.19.855001@cox.net> (raw)
In-Reply-To: 20040829214235.5115ef57.spider@gentoo.org

Spider posted <20040829214235.5115ef57.spider@gentoo.org>, excerpted
below,  on Sun, 29 Aug 2004 21:42:35 +0200:

> begin  quote
> On Thu, 26 Aug 2004 17:56:56 +0200
> Carsten Lohrke <carlo@gentoo.org> wrote:
> 
>> The kde herd wants to give everyone the possibility to configure with
>> --enable-final via the "final" use flag. Additionally I thought about a 
>> kde-misc category, which would include a bunch of kde related packages,
>> which  are now mainly placed in app-misc, x11-misc, some in other
>> categories and a  few are still in bugs.g.o.
> 
>>  Any objections?
>> 
>> 
> I'd object to the use of the word "final" for this, since its ambigous and
> hard to comprehend its meaning.  I'd suggest finding a better word to
> describe the flag and its function.

The trouble is that's the upstream choice.  From kdebase 3.3.0's
./configure --help:

 --enable-final  build size optimized apps (experimental [...])
    
Isn't one of the Gentoo policies to let upstream policy guide where
possible in such instances?  Anyone that has worked on KDE sources should
instantly grok what such a use flag is about.  If Gentoo calls it
something else, it will IMO make things /less/ clear.

Well, I guess the /one/ simpler possibility would be to call the flag
"enable-final", instead of simply "final", making it even clearer, but I'd
expect that wouldn't address your concern.

-- 
Duncan - List replies preferred.   No HTML msgs.
"They that can give up essential liberty to obtain a little
temporary safety, deserve neither liberty nor safety." --
Benjamin Franklin



--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2004-08-30  8:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-26 15:56 [gentoo-dev] new global use flag and a new category Carsten Lohrke
2004-08-26 16:02 ` Ciaran McCreesh
2004-08-26 16:41   ` Carsten Lohrke
2004-08-26 16:46     ` Caleb Tennis
2004-08-27 13:08 ` Mike Frysinger
2004-08-28 22:31   ` Carsten Lohrke
2004-08-29 17:44     ` Mike Frysinger
2004-08-29 18:10       ` Carsten Lohrke
2004-08-29 18:32         ` Mike Frysinger
2004-08-30 10:05           ` Paul de Vrieze
2004-08-28  9:58 ` Markus Nigbur
2004-08-29 19:42 ` Spider
2004-08-30  8:51   ` Duncan [this message]
2004-08-30 11:07     ` [gentoo-dev] " Mike Frysinger
2004-08-30 14:33   ` [gentoo-dev] " Carsten Lohrke
2004-09-01 20:47     ` 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=pan.2004.08.30.08.51.19.855001@cox.net \
    --to=1i5t5.duncan@cox.net \
    --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