From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New local or global USE flags for sdl bindings: noimage & nomixer
Date: Wed, 25 Aug 2004 18:14:10 -0400 [thread overview]
Message-ID: <200408251814.14791.vapier@gentoo.org> (raw)
In-Reply-To: <200408251628.22318.mattam@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1690 bytes --]
On Wednesday 25 August 2004 10:28 am, Matthieu Sozeau wrote:
> so... i have the choice of using no* local flags or setup make.defaults
> with sdl-image and sdl-mixer global flags. I find those a little too
> specific to make it in make.defaults, so i wouldn't mind using no* flags as
> a temporary solution (and i will if no one objects). Adding a + syntax to
> use. {local.}desc, like "dev-ml/ocamlsdl:+image - Adds support for
> sdl-image (unset at your own risk)" would be useful (that is it would
> completely solve the no* flags problem).
actually, how is this for an idea ...
instead of a file many people would have to update and sync across different
profiles (huge pita, look at some of the virtual issues for example), what
about if we extend the IUSE syntax ? then maintainers of their own ebuilds
can determine 'default' USE setting on a per-package and even per-version
basis ...
for example i'll use nano since i maintain it:
IUSE="nls build spell justify debug slang ncurses nomac"
here we will consider 'justify' and 'nomac' ... the defaults from upstream is
to enable justify and mac conversion support ... however, as the maintainer
of the ebuild, i've selected disabling justify and enabling mac conversion as
the defaults, generating the ugly 'nomac' in the process ... in the new
world, i'd utilize this:
IUSE="nls build spell +justify debug slang ncurses +mac"
now, whenever a user does not have 'justify' or 'mac' in their USE, either in
the positive (USE=justify) or in the negative (USE=-justify), portage would
turn around and add justify and mac to USE for this package/version for us
what do you guys think ?
-mike
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 838 bytes --]
next prev parent reply other threads:[~2004-08-25 22:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-23 14:53 [gentoo-dev] New local or global USE flags for sdl bindings: noimage & nomixer Matthieu Sozeau
2004-08-23 15:14 ` Carsten Lohrke
2004-08-23 15:40 ` Mike Frysinger
2004-08-23 16:07 ` Carsten Lohrke
2004-08-23 16:15 ` Mike Frysinger
2004-08-23 18:07 ` Carsten Lohrke
2004-08-23 18:26 ` Mike Frysinger
2004-08-23 18:34 ` Carsten Lohrke
2004-08-23 23:50 ` Mike Frysinger
2004-08-23 23:55 ` Carsten Lohrke
2004-08-24 0:00 ` Mike Frysinger
2004-08-25 8:25 ` Donnie Berkholz
2004-08-25 14:44 ` Mike Frysinger
2004-08-23 15:58 ` Matthieu Sozeau
2004-08-23 18:13 ` Carsten Lohrke
2004-08-23 18:14 ` Marius Mauch
2004-08-23 18:41 ` Carsten Lohrke
2004-08-25 14:28 ` Matthieu Sozeau
2004-08-25 22:14 ` Mike Frysinger [this message]
2004-08-25 22:29 ` Carsten Lohrke
2004-08-26 3:11 ` Andrew Ross
2004-08-26 6:21 ` Mike Frysinger
2004-08-25 22:29 ` Spider
2004-08-27 12:29 ` Paul de Vrieze
2004-08-26 14:41 ` Eldad Zack
2004-08-27 12:23 ` Paul de Vrieze
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=200408251814.14791.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