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
| Navigation: |
|
Lists:
gentoo-dev:
< Prev
By Thread
Next >
< Prev
By Date
Next >
|
| Headers: |
|
To:
|
gentoo-dev@g.o
|
|
From:
|
Ciaran McCreesh <ciaran.mccreesh@...>
|
|
Subject:
|
Re: Re: RFC: Making backwards-incompatible tree changes | a solution for GLEP 55's problem
|
|
Date:
|
Tue, 20 Sep 2011 11:40:13 +0100
|
|
On Tue, 20 Sep 2011 03:28:48 -0700
Brian Harring <ferringb@...> wrote:
> Paludis wise, it's eapi2 indirictely due to boost and eselect.
> Looking at the eapi depgraph for that, doesn't look particularly
> viable for upgrading from a EAPI<2 manager for paludis. I'll leave
> it to Ciaran to comment on the feasability of a static rescue
> binary (or extremely simplified upgrade pathway).
boost's just for Python bindings, which are optional. The eselect
dependency is hard, and can't easily be made optional, so ideally
eselect should stick with older EAPIs.
Maybe we should stick something in metadata.xml...
--
Ciaran McCreesh
|
|
