From: Martin Schlemmer <azarah@nosferatu.za.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Improved ebuild information
Date: Wed, 05 Oct 2005 20:03:54 +0200 [thread overview]
Message-ID: <1128535434.7199.6.camel@lycan.lan> (raw)
In-Reply-To: <20051001212202.3e7537f3@snowdrop.home>
[-- Attachment #1: Type: text/plain, Size: 1234 bytes --]
On Sat, 2005-10-01 at 21:22 +0100, Ciaran McCreesh wrote:
> On Sat, 01 Oct 2005 22:19:39 +0200 Daniel Stiefelmaier
> <mail@stiefelweb.de> wrote:
> | I'd like to have a functionality that prints out what the useflags of
> | a ebuild are good for. Some are obvious, others are not. Example:
> | The useflag "xprint" sounds like printing support, but doesn't tell
> | if you need it if you use cups or the kde-printing system or...
> | whatever.
>
> We've discussed adding this to metadata.xml a few times in the past,
> but every time there was opposition from a vocal minority of one who
> claimed that USE flags should always do exactly the same thing for
> every package.
>
I guess I am one of this 'minority'. The question I just want to have
answered, is how the hell are you going to get a system up sanely (and
without tweaking /etc/portage/package.use) if besides the 350 global USE
flags, and the 1200 local USE flags, you now have to worry about global
USE flags meaning different things for every package?
As for the 'xprint' USE flags ... I guess the description is
deceptive .. its support for X11's printing system (or should be).
'cups' is for cups support, etc.
--
Martin Schlemmer
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-10-05 18:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-01 20:19 [gentoo-dev] Improved ebuild information Daniel Stiefelmaier
2005-10-01 20:22 ` Ciaran McCreesh
2005-10-02 0:10 ` Daniel Stiefelmaier
2005-10-02 6:06 ` Chris Gianelloni
2005-10-05 18:03 ` Martin Schlemmer [this message]
2005-10-05 18:34 ` Ciaran McCreesh
2005-10-05 21:13 ` [gentoo-dev] " R Hill
2005-10-10 12:53 ` Chris Gianelloni
2005-10-10 17:36 ` Bruno
2005-10-10 19:02 ` Apreche
2005-10-10 19:23 ` R Hill
2005-10-10 19:56 ` Thomas de Grenier de Latour
2005-10-01 20:25 ` [gentoo-dev] " Simon Stelling
2005-10-02 0:46 ` Daniel Stiefelmaier
2005-10-02 2:35 ` Alec Warner
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=1128535434.7199.6.camel@lycan.lan \
--to=azarah@nosferatu.za.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