From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: PROPERTIES=funky-slots
Date: Sat, 23 Jun 2012 19:57:07 +0200 [thread overview]
Message-ID: <1340474227.5979.78.camel@belkin4> (raw)
In-Reply-To: <20120623184546.56f49e58@googlemail.com>
[-- Attachment #1: Type: text/plain, Size: 1094 bytes --]
El sáb, 23-06-2012 a las 18:45 +0100, Ciaran McCreesh escribió:
> On Sat, 23 Jun 2012 19:43:10 +0200
> Pacho Ramos <pacho@gentoo.org> wrote:
> > > It treats -r300 as being newer than -r200, and so will treat "the
> > > gtk3 version" or "the jruby version" as being newer versions of
> > > "the gtk2 version" or "the ruby 1.8 version", just as it tries to
> > > bring in a newer GCC and so on.
> >
> > And what problems is that causing for you?
>
> The problem is that there's no way of knowing that -r300 is not "a
> newer version" than -r200, and that the jruby implementation is not "a
> newer version" than the ruby 1.8 implementation.
>
Regarding -r300 issue (I don't know much about ruby), I guess paludis
wants to install net-libs/webkit-gtk-1.8.1-r301 for example when nothing
is requiring any specific SLOT? What problems does it cause apart of
what would cause if ebuilds using gtk2 are RDEPENDing on plain
x11-libs/gtk+ without specifying any SLOT? In both cases gtk2 apps
should RDEPEND specifically in SLOTs for gtk2 support and gtk3 apps on
gtk3 slots.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-06-23 17:58 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-23 13:21 [gentoo-dev] RFC: PROPERTIES=funky-slots Ciaran McCreesh
2012-06-23 14:02 ` Mike Gilbert
2012-06-23 14:06 ` Mike Gilbert
2012-06-23 14:10 ` Ciaran McCreesh
2012-06-23 14:20 ` Mart Raudsepp
2012-06-23 16:12 ` Ciaran McCreesh
2012-06-24 17:25 ` Alexis Ballier
2012-06-23 15:51 ` Michał Górny
2012-06-23 16:08 ` Ciaran McCreesh
2012-06-23 20:36 ` Marien Zwart
2012-06-23 20:37 ` Ciaran McCreesh
2012-06-24 8:19 ` Michał Górny
2012-06-24 10:58 ` Ciaran McCreesh
2012-06-24 11:21 ` Michał Górny
2012-06-24 11:23 ` Ciaran McCreesh
2012-06-27 7:44 ` Gilles Dartiguelongue
2012-06-23 16:13 ` Justin
2012-06-23 16:17 ` Ciaran McCreesh
2012-06-23 16:47 ` Justin
2012-06-23 16:53 ` Ciaran McCreesh
2012-06-23 17:14 ` Justin
2012-06-23 17:23 ` Pacho Ramos
2012-06-23 17:30 ` Ciaran McCreesh
2012-06-23 17:43 ` Pacho Ramos
2012-06-23 17:45 ` Ciaran McCreesh
2012-06-23 17:54 ` Michał Górny
2012-06-23 17:56 ` Ciaran McCreesh
2012-06-23 18:09 ` Michał Górny
2012-06-23 18:06 ` Ciaran McCreesh
2012-06-23 18:23 ` Michał Górny
2012-06-23 18:22 ` Ciaran McCreesh
2012-06-23 18:35 ` Alex Alexander
2012-06-23 18:37 ` Ciaran McCreesh
2012-06-23 19:14 ` Alex Alexander
2012-06-23 19:16 ` Ciaran McCreesh
2012-06-23 19:27 ` Alex Alexander
2012-06-23 19:29 ` Ciaran McCreesh
2012-06-23 18:37 ` Michał Górny
2012-06-28 5:03 ` Matt Turner
2012-06-28 6:24 ` Ben de Groot
2012-06-23 17:57 ` Pacho Ramos [this message]
2012-06-23 22:50 ` Gilles Dartiguelongue
2012-06-24 8:48 ` Ben de Groot
2012-06-24 10:17 ` Gilles Dartiguelongue
2012-06-23 17:16 ` Alec Warner
2012-06-23 17:24 ` Ciaran McCreesh
2012-06-23 17:35 ` Alec Warner
2012-06-23 17:36 ` Ciaran McCreesh
2012-06-23 17:34 ` Kent Fredric
2012-06-23 16:26 ` Patrick Lauer
2012-09-03 14:08 ` [gentoo-dev] " Mark Bateman
2012-09-06 8:21 ` 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=1340474227.5979.78.camel@belkin4 \
--to=pacho@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