On 05/01/2013 02:07 AM, Jörg Schaible wrote:
> Hi Zac,
>
> Zac Medico wrote:
>
>> On Tue, Apr 30, 2013 at 9:51 AM, Jörg Schaible <joerg.schai...@gmx.de>
>> wrote:
>>> The most annoying fact is, that none of this would have been necessary
>>> with portage 2.2, but maybe we have to wait for 2.1.11.500 before 2.2
>>> gets stable...
>>
>> Since portage-2.1.11.20 [1], you can do this:
>>
>> echo 'FEATURES="${FEATURES} preserve-libs"' >> /etc/portage/make.conf
>>
>> [1]
>> [http://blogs.gentoo.org/zmedico/2012/09/21/preserve-libs-available-in-portage-2-1/
>
> That announcement slipped somehow my awareness. Indeed an upgrade of a
> different machine with preserve-libs added to FEATURES went fine. Still, I
> wonder what prevents portage-2.2 form going stable, I have one machine where
> I use that one for years without any flaws and a lot of benefits.
I think it's more useful to talk about specific features and their
readiness to be enabled by default in stable, rather then when
"everything in portage-2.2" should go stable. Which features in
portage-2.2 are you using that are ready for stable?
Not that the difference between portage-2.1 and portage-2.2 is just the
constants that you can see in this commit:
http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=92ce3fcbf2c6d791151afc6edbbb18a530db12e2
--
Thanks,
Zac
