Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Michał Górny <mgorny@g.o>
Subject: Re: RFC: PROPERTIES=funky-slots
Date: Sun, 24 Jun 2012 13:21:01 +0200
On Sun, 24 Jun 2012 11:58:07 +0100
Ciaran McCreesh <ciaran.mccreesh@...> wrote:

> On Sun, 24 Jun 2012 10:19:19 +0200
> Michał Górny <mgorny@g.o> wrote:
> > > Think || ( a:3 a:2 ).
> > 
> > So now that you've stated the problem, maybe it's a good time to
> > find a proper solution for it.
> 
> That isn't the problem. That's an example of an effect of the problem.
> The problem is that -r and slots are being used to do something weird.

No? What will paludis do in the above case, if the newest version of a
has slot :4?


-- 
Best regards,
Michał Górny
Attachment:
signature.asc (PGP signature)
Replies:
Re: RFC: PROPERTIES=funky-slots
-- Ciaran McCreesh
References:
RFC: PROPERTIES=funky-slots
-- Ciaran McCreesh
Re: RFC: PROPERTIES=funky-slots
-- Mike Gilbert
Re: RFC: PROPERTIES=funky-slots
-- Mike Gilbert
Re: RFC: PROPERTIES=funky-slots
-- Ciaran McCreesh
Re: RFC: PROPERTIES=funky-slots
-- Michał Górny
Re: RFC: PROPERTIES=funky-slots
-- Ciaran McCreesh
Re: RFC: PROPERTIES=funky-slots
-- Marien Zwart
Re: RFC: PROPERTIES=funky-slots
-- Ciaran McCreesh
Re: RFC: PROPERTIES=funky-slots
-- Michał Górny
Re: RFC: PROPERTIES=funky-slots
-- Ciaran McCreesh
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: RFC: PROPERTIES=funky-slots
Next by thread:
Re: RFC: PROPERTIES=funky-slots
Previous by date:
Re: RFC: PROPERTIES=funky-slots
Next by date:
Re: net-libs/libmicrohttpd up for grabs


Updated Jun 29, 2012

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.