From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: new global use flag and a new category
Date: Mon, 30 Aug 2004 07:07:39 -0400 [thread overview]
Message-ID: <200408300707.48065.vapier@gentoo.org> (raw)
In-Reply-To: <pan.2004.08.30.08.51.19.855001@cox.net>
[-- Attachment #1: Type: text/plain, Size: 856 bytes --]
On Monday 30 August 2004 04:51 am, Duncan wrote:
> 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.
no, we have no policy on upstream naming conventions -> USE naming
conventions ... our policy is to make the USE flags generally clear as to
what their intent is
you can just as easily call it 'kde-blahblah-flag' and then run `use_enable
kde-blahblah-flag final` and get the same results as if you had called it
'final' and run `use_enable final`
-mike
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 838 bytes --]
next prev parent reply other threads:[~2004-08-30 11:07 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 ` [gentoo-dev] " Duncan
2004-08-30 11:07 ` Mike Frysinger [this message]
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=200408300707.48065.vapier@gentoo.org \
--to=vapier@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