1 |
On Tue, Sep 20, 2011 at 11:40:13AM +0100, Ciaran McCreesh wrote: |
2 |
> On Tue, 20 Sep 2011 03:28:48 -0700 |
3 |
> Brian Harring <ferringb@×××××.com> wrote: |
4 |
> > Paludis wise, it's eapi2 indirictely due to boost and eselect. |
5 |
> > Looking at the eapi depgraph for that, doesn't look particularly |
6 |
> > viable for upgrading from a EAPI<2 manager for paludis. I'll leave |
7 |
> > it to Ciaran to comment on the feasability of a static rescue |
8 |
> > binary (or extremely simplified upgrade pathway). |
9 |
> |
10 |
> boost's just for Python bindings, which are optional. The eselect |
11 |
> dependency is hard, and can't easily be made optional, so ideally |
12 |
> eselect should stick with older EAPIs. |
13 |
|
14 |
Bit more than just that, going by a quick look. libpcre is 3/4; |
15 |
looks like an old version is intentionally held back. pkgconfig is |
16 |
the same- 0.25-r2 is EAPI2, everything else is EAPI4. |
17 |
|
18 |
You didn't answer the static question btw... |
19 |
~brian |