From: Brian Harring <ferringb@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: RFC: Making backwards-incompatible tree changes | a solution for GLEP 55's problem
Date: Tue, 20 Sep 2011 04:07:44 -0700 [thread overview]
Message-ID: <20110920110744.GB6252@localhost> (raw)
In-Reply-To: <20110920114013.5c2b69dc@googlemail.com>
On Tue, Sep 20, 2011 at 11:40:13AM +0100, Ciaran McCreesh wrote:
> On Tue, 20 Sep 2011 03:28:48 -0700
> Brian Harring <ferringb@gmail.com> 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.
Bit more than just that, going by a quick look. libpcre is 3/4;
looks like an old version is intentionally held back. pkgconfig is
the same- 0.25-r2 is EAPI2, everything else is EAPI4.
You didn't answer the static question btw...
~brian
next prev parent reply other threads:[~2011-09-20 11:08 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-19 22:14 [gentoo-dev] RFC: Making backwards-incompatible tree changes | a solution for GLEP 55's problem Alex Alexander
2011-09-19 22:53 ` [gentoo-dev] " Duncan
2011-09-20 0:46 ` Rich Freeman
2011-09-20 1:44 ` Duncan
2011-09-20 7:12 ` Alex Alexander
2011-09-20 10:43 ` Patrick Lauer
2011-09-20 10:28 ` Brian Harring
2011-09-20 10:40 ` Ciaran McCreesh
2011-09-20 11:07 ` Brian Harring [this message]
2011-09-20 11:27 ` Ciaran McCreesh
2011-09-20 13:33 ` Ulrich Mueller
2011-09-20 10:50 ` Dirkjan Ochtman
2011-09-20 6:56 ` Alex Alexander
2011-09-20 13:09 ` [gentoo-dev] " Pacho Ramos
2011-09-20 13:16 ` Pacho Ramos
2011-09-20 13:16 ` Michał Górny
2011-09-20 13:25 ` Pacho Ramos
2011-09-20 13:57 ` [gentoo-dev] " Duncan
2011-09-20 14:23 ` Pacho Ramos
2011-09-20 17:00 ` [gentoo-dev] " Patrick Lauer
2011-09-21 4:00 ` [gentoo-dev] " Duncan
2011-09-21 13:24 ` Pacho Ramos
2011-09-20 15:19 ` [gentoo-dev] " Zac Medico
2011-09-20 15:28 ` Zac Medico
2011-09-20 17:03 ` Patrick Lauer
2011-09-20 17:14 ` Rich Freeman
2011-09-20 17:48 ` Alec Warner
2011-09-20 20:03 ` Michał Górny
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=20110920110744.GB6252@localhost \
--to=ferringb@gmail.com \
--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