From: Andrew Muraco <tuxp3@leetworks.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Default useflag cleanups: -apm -foomaticdb -fortran -imlib -motif -oss -xmms
Date: Mon, 05 Jun 2006 22:45:57 -0400 [thread overview]
Message-ID: <4484EC65.8020805@leetworks.com> (raw)
In-Reply-To: <200606052145.27898.carlo@gentoo.org>
Carsten Lohrke wrote:
>On Monday 05 June 2006 20:08, Harald van Dijk wrote:
>
>
>>No, the decision with the gtk/gtk2 USE flag mess was to have package
>>maintainers decide for each ebuild whether to support only gtk1 or only
>>gtk2, but not have support for both in a single ebuild.
>>
>>
>
>I know about the decision of the Gnome team, but there also was a thread with
>maintainers refusing to remove optional gtk1|2 support, if I recall
>correctly. Personally I couldn't care less, as long as the gtk2 flag is
>history.
>
>
Sorry for the offtopic of this, but what would a user set as the
useflags to have GTK-2 used by default, and GTK-1 for apps that only
support it? (but not build GTK-2-capable apps with GTK-1)
Just wondering, because I know that gmplayer is from the mplayer
package's gtk flag.. its gtk-1 so its not the optimal, but since i don't
know of a gtk2 version (i do have kmplayer tho.. so its sorta a moot
point for me.. i think its time i clean my install..)
Anyways, I agree that some of the defaults are a bit more liberal then i
would perfer, but hey, i can change anything i want (thats the power of
gentoo)
Thanks,
Andrew
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2006-06-06 2:52 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-05 16:03 [gentoo-dev] Default useflag cleanups: -apm -foomaticdb -fortran -imlib -motif -oss -xmms Stefan Schweizer
2006-06-05 16:16 ` Patrick McLean
2006-06-06 3:58 ` Mike Frysinger
2006-06-05 16:16 ` Grant Goodyear
2006-06-05 16:33 ` Harald van Dijk
2006-06-05 16:59 ` Carsten Lohrke
2006-06-05 18:08 ` Harald van Dijk
2006-06-05 19:45 ` Carsten Lohrke
2006-06-06 2:45 ` Andrew Muraco [this message]
2006-06-06 9:16 ` Carsten Lohrke
2006-06-05 18:36 ` George Shapovalov
2006-06-05 18:52 ` Chris Gianelloni
2006-06-05 19:57 ` Carsten Lohrke
2006-06-05 21:25 ` Chris Gianelloni
2006-06-05 22:18 ` Carsten Lohrke
2006-06-05 19:22 ` Wernfried Haas
2006-06-05 19:58 ` Luis Medinas
2006-06-05 20:50 ` Wernfried Haas
2006-06-08 8:30 ` Robin H. Johnson
2006-06-08 10:30 ` Luis Medinas
2006-06-08 10:15 ` Mike Frysinger
2006-06-06 1:23 ` Chris Gianelloni
2006-06-06 2:10 ` [gentoo-dev] " Stefan Schweizer
2006-06-06 2:31 ` Chris Gianelloni
2006-06-06 6:47 ` Doug Goldstein
2006-06-06 14:38 ` Mike Doty
2006-06-06 2:11 ` Michael Sterrett -Mr. Bones.-
2006-06-06 9:19 ` Carsten Lohrke
2006-06-06 4:07 ` [gentoo-dev] " Mike Frysinger
2006-06-06 5:31 ` Harald van Dijk
2006-06-06 5:48 ` Mike Frysinger
2006-06-06 6:13 ` Harald van Dijk
2006-06-06 6:34 ` John Myers
2006-06-06 9:26 ` Diego 'Flameeyes' Pettenò
2006-06-07 9:42 ` Mike Frysinger
2006-06-06 9:17 ` Carsten Lohrke
2006-06-06 9:25 ` Diego 'Flameeyes' Pettenò
2006-06-06 10:14 ` Carsten Lohrke
2006-06-06 15:43 ` Chris Gianelloni
2006-06-06 6:40 ` Thomas de Grenier de Latour
2006-06-06 15:44 ` Chris Gianelloni
2006-06-06 4:00 ` Mike Frysinger
2006-06-06 6:51 ` Doug Goldstein
2006-06-06 16:24 ` Jason Wever
2006-06-06 23:05 ` Danny van Dyk
2006-06-07 0:37 ` Chris Gianelloni
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=4484EC65.8020805@leetworks.com \
--to=tuxp3@leetworks.com \
--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