public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Albert Hopkins <marduk@letterboxes.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Is Gentoo wiping out Gtk 2 support from packages that support it?
Date: Fri, 08 Jul 2011 09:14:36 -0400	[thread overview]
Message-ID: <1310130876.229332.5.camel@localhost.localdomain> (raw)
In-Reply-To: <B20B5F33-4E81-40B3-9B45-BDDAD8DC6603@stellar.eclipse.co.uk>



On Friday, July 8 at 13:11 (+0100), Stroller said:

> Taking a look at this bug today, is there any reason why the ebuild
> shouldn't simply RDEPEND="x11-libs/gtk+" (i.e. remove the explicit dep
> on gtk3), detect what version you have installed on your system and
> then either run --enable-gtk3 or --enable-gtk2 during src_configure(),
> depending upon which you're using?
> 
ebuilds generally don't do this, because it is bad.  What you have and
what you want aren't necessarily the same thing.  Consider:

      * You don't yet have any gtk installed
      * You have gtk2 but actually *want* the gtk3 version, so you want
        the ebuild to pull in gtk3 (or vice versa)
      * You have both gtk2 and gtk3 installed.
      * You have gtk installed, but don't want gtk support for a
        particular package (if gtk support is optional for that
        package).






  reply	other threads:[~2011-07-08 14:06 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-06 16:35 [gentoo-user] Is Gentoo wiping out Gtk 2 support from packages that support it? Nikos Chantziaras
2011-07-06 17:23 ` pk
2011-07-06 19:37   ` Alan McKinnon
2011-07-06 20:02     ` pk
2011-07-06 20:41       ` Alan McKinnon
2011-07-06 22:53         ` Volker Armin Hemmann
2011-07-06 23:06           ` Dale
2011-07-06 23:20             ` Peter Humphrey
2011-07-06 23:21             ` [gentoo-user] " Nikos Chantziaras
2011-07-07  3:04               ` Dale
2011-07-07 17:42     ` [gentoo-user] " Michael Orlitzky
2011-07-07 19:36       ` Alan McKinnon
2011-07-07 20:01         ` Michael Orlitzky
2011-07-07 20:47           ` Dale
2011-07-07 20:57             ` Peter Humphrey
2011-07-07 21:03               ` Dale
2011-07-08  4:42           ` 微菜
2011-07-06 18:02 ` Volker Armin Hemmann
2011-07-07  2:12 ` 微菜
2011-07-07  2:45   ` [gentoo-user] " Nikos Chantziaras
2011-07-07  3:31     ` 微菜
2011-07-07  7:30   ` [gentoo-user] " Alan McKinnon
2011-07-07 12:07     ` Stroller
2011-07-07 22:50       ` [gentoo-user] " walt
2011-07-07 23:40         ` Neil Bothwick
2011-07-07 16:44     ` [gentoo-user] " pk
2011-07-07 17:14       ` Mark Knecht
2011-07-07 23:52     ` [gentoo-user] " Nikos Chantziaras
2011-07-08 12:11 ` [gentoo-user] " Stroller
2011-07-08 13:14   ` Albert Hopkins [this message]
2011-07-08 15:19     ` Alan McKinnon
2011-07-08 17:39       ` Stroller
2011-07-09  7:26         ` Alan McKinnon
2011-07-09 14:02           ` [gentoo-user] " Nikos Chantziaras
2011-07-08 17:50       ` Nikos Chantziaras
2011-07-08 19:06       ` [gentoo-user] " Albert Hopkins
2011-07-08 20:32         ` Stroller
2011-07-09 16:28       ` William Hubbs
2011-07-09 20:24         ` Alan McKinnon
2011-07-08 18:03     ` Stroller
2011-07-08 13:37   ` [gentoo-user] " Nikos Chantziaras

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=1310130876.229332.5.camel@localhost.localdomain \
    --to=marduk@letterboxes.org \
    --cc=gentoo-user@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