From: Brian Harring <ferringb@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] GTK und GTK2 Use Flag
Date: Tue, 29 Mar 2005 05:11:44 -0600 [thread overview]
Message-ID: <20050329111142.GA29694@exodus> (raw)
In-Reply-To: <20050329105857.GA9909@stud.seeling33.de>
On Tue, Mar 29, 2005 at 12:58:57PM +0200, Stefan Sperling wrote:
> On Tue, Mar 29, 2005 at 12:15:17PM +0200, Fabian Zeindl wrote:
> > Hello
> >
> > There was a discussion on the gentoo-user-de list about this two
> > Useflags: gtk and gtk2. Because not everybody is sure what the mean, so
> > if you have -gtk +gtk2 some think that gtk2 should be installed and soon.
>
> There are lots of useflags that don't install anything.
> Take the new mp3 useflag for example, used by beep-media-player.
> would you expect it to install a program called 'mp3'? :)
>
> > Wouldn't it be better if "gtk" meaned that the newest available gtk
> > version ist installed (gtk1 or gtk2) and a flag like oldgtk take the
> > older version gtk1.
>
> As soon as gtk3 comes along, you scheme won't work anymore.
>
> Some programs use gtk1 only, some gtk2 only, and a few have
> support for both. As there is not much point in using both
> of them at runtime, if you use +gtk2, programs that support
> both will use gtk2.
A saner (and previously proposed) approach would be
gtk ~= gtk support. *any* version.
gtk1 = gtk v1 support
gtk2 = gtk v2 support
gtkN = gtk vN support.
With the current approach, gtk2 is dependant on gtk; above approach
breaks the dependency between the two flags, and gives the user the
ability to control explicitly what versions are used, rather then the
partial crapshoot it is now. If they want *just* v2 support, above
allows it w/out resorting to a package.mask.
~brian
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-03-29 11:11 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-29 10:15 [gentoo-dev] GTK und GTK2 Use Flag Fabian Zeindl
2005-03-29 10:58 ` Stefan Sperling
2005-03-29 11:04 ` Diego "Flameeyes" Pettenò
2005-03-29 11:11 ` Stefan Sperling
2005-03-29 11:24 ` Diego "Flameeyes" Pettenò
2005-03-29 11:35 ` David Morgan
2005-03-29 11:50 ` Brian Harring
2005-03-29 13:09 ` David Morgan
2005-03-29 13:39 ` Brian Harring
2005-03-29 14:19 ` David Morgan
2005-03-29 15:38 ` Stefan Sperling
2005-03-29 17:20 ` Markus Nigbur
2005-03-29 21:35 ` foser
2005-03-29 21:42 ` Ciaran McCreesh
2005-03-30 9:00 ` Paul de Vrieze
2005-03-29 22:29 ` Brian Harring
2005-03-29 22:46 ` Ciaran McCreesh
2005-03-29 23:09 ` Olivier Crête
2005-03-29 23:13 ` foser
2005-03-29 23:33 ` Brian Harring
2005-03-30 4:32 ` Dulmandakh Sukhbaatar
2005-03-30 8:44 ` Diego "Flameeyes" Pettenò
2005-03-29 11:05 ` Stefan Sperling
2005-03-29 11:11 ` Brian Harring [this message]
2005-03-29 20:49 ` Spider
2005-03-29 22:43 ` Brian Harring
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=20050329111142.GA29694@exodus \
--to=ferringb@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-dev@robin.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