From: "Noack, Sebastian" <S.Noack@AUTOonline.de>
To: <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] Proposal for advanced useflag-syntax
Date: Thu, 3 Aug 2006 13:31:37 +0200 [thread overview]
Message-ID: <7B97065F451A23458ED0C63B4CA5A2EA1D2911@SRV-EXCHANGE.AUTOonline.local> (raw)
Hi,
following szenario: Somebody installs a kde desktop and because of it is
an 80 years old woman ;), she wants to have graphical frontends where
ever possible.
Today the solution would be to enable the kde, qt, qt3, qt4, gtk, etc.
-useflag. But this solution is crappy, because of some ebuilds for
example app-office/openoffice have support for multiple widget libraries
and because our 80 years old female person has a kde desktop, she would
prefer kde-support about gtk+. Today she would have to decide if she
wants to make an entry in /etc/portage/package.use for each ebuild that
comes with multiple widget library support or if she wants to compile
each such ebuild preventive with support for every available widget
library, which would be against the sense of useflags.
To prevent such szenarios I propose following extended syntax for
useflag configuration:
(kde || qt4 || qt3 || qt || gtk) (arts || alsa) (asf && win32codecs)
This expression would affect that only if a kde-useflag isn't provided
the qt4 useflag, becomes used and if this isn't also provided the qt3
useflag becomes used and so on. The same for arts and alsa, where it is
nonsense to support both but better to support arts. And the last
segment of this expression would affect that win32codecs and asf becomes
enabled for each ebuild that supports asf. This would for example be
useful in the case of media-libs/xine-lib if you want have asf-support
but you want avoid win32codecs as much as possible, because of xine-lib
needs win32codecs to support asf.
Best Regards
Sebasitan Noack
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2006-08-03 11:35 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 11:31 Noack, Sebastian [this message]
[not found] ` <20060803153407.GA19696@nibiru.local>
2006-08-03 18:38 ` [gentoo-dev] Proposal for advanced useflag-syntax Luca Barbato
[not found] ` <20060807131642.GF25236@nibiru.local>
2006-08-07 13:40 ` Paul de Vrieze
2006-08-07 14:18 ` Enrico Weigelt
2006-08-07 10:58 ` Alec Warner
2006-08-07 16:40 ` [gentoo-dev] " Duncan
2006-08-07 21:08 ` [gentoo-dev] " Paul de Vrieze
2006-08-08 10:30 ` Enrico Weigelt
2006-08-08 10:39 ` Simon Stelling
2006-08-08 10:58 ` Enrico Weigelt
2006-08-08 10:57 ` Jakub Moc
2006-08-04 7:54 ` Simon Stelling
2006-08-04 9:01 ` Brian Harring
2006-08-07 13:48 ` Enrico Weigelt
2006-08-07 14:08 ` Stephen P. Becker
2006-08-08 1:44 ` W.Kenworthy
2006-08-08 2:14 ` Mike Frysinger
2006-08-08 10:34 ` Enrico Weigelt
2006-08-08 2:50 ` Donnie Berkholz
2006-08-08 10:40 ` Enrico Weigelt
2006-08-08 12:37 ` Jan Kundrat
2006-08-08 14:50 ` Enrico Weigelt
2006-08-08 15:06 ` Lance Albertson
2006-08-08 20:17 ` Enrico Weigelt
2006-08-08 20:37 ` Lance Albertson
2006-08-08 20:46 ` Jan Kundrát
2006-08-08 21:22 ` Curtis Napier
2006-08-08 15:12 ` Thomas Cort
2006-08-08 20:22 ` Enrico Weigelt
2006-08-08 21:02 ` Richard Fish
-- strict thread matches above, loose matches on Subject: below --
2006-08-04 6:21 AW: " Noack, Sebastian
2006-08-07 13:26 ` Enrico Weigelt
2006-08-07 14:53 ` Thomas Cort
2006-08-07 18:48 ` Enrico Weigelt
2006-08-07 20:09 ` Marius Mauch
2006-08-07 21:14 ` Paul de Vrieze
2006-08-07 15:04 AW: " Noack, Sebastian
2006-08-07 20:18 ` Enrico Weigelt
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=7B97065F451A23458ED0C63B4CA5A2EA1D2911@SRV-EXCHANGE.AUTOonline.local \
--to=s.noack@autoonline.de \
--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