В Втр, 28/06/2011 в 07:17 +0100, Ciaran McCreesh пишет:
> There was going to be a really simple, elegant, ebuild-controllable and
> provably working fix for that in EAPI 4 in the form of := deps, but
> they got dropped because Portage couldn't implement it.
>
> Which is strange, because it should
On Tue, 28 Jun 2011 16:54:43 +1200
Kent Fredric wrote:
> Reminds me of the other awkward behaviour I once hit where a package
> depends on something that is slotted, and mysteriously uses a middle
> version of the things that are slotted, and then breaks with that
> version that it for some myster
On 28 June 2011 04:44, Graham Murray wrote:
> Ciaran McCreesh writes:
>
>> The fix for that is to slot things properly. You're screwed anyway if a
>> preserved library tries to access installed data that has either been
>> removed or upgraded to a new format that it doesn't recognise.
>
> Or some
Ciaran McCreesh writes:
> The fix for that is to slot things properly. You're screwed anyway if a
> preserved library tries to access installed data that has either been
> removed or upgraded to a new format that it doesn't recognise.
Or some "awkward" packages which when rebuilt will still link
On Sun, 26 Jun 2011 16:42:51 +0200
Fabian Groffen wrote:
> On 26-06-2011 14:31:12 +, Duncan wrote:
> > > Hmmm, except that portage-2.2 isn't stable yet... indeed it isn't
> > > even out of alpha yet. Not going to unleash that on my
> > > production systems.
> >
> > Besides portage-2.2 still
On 26-06-2011 14:31:12 +, Duncan wrote:
> > Hmmm, except that portage-2.2 isn't stable yet... indeed it isn't even
> > out of alpha yet. Not going to unleash that on my production systems.
>
> Besides portage-2.2 still being unstable, preserved-libs "solves" the
> problem by keeping outdated
