Marius Mauch a écrit :
So, do you think it should be enabled by default?
Does portage have a way to report which libraries it is keeping around
because of preserve-libs ? If there's an easy way to figure that out,
then enabling it by default is a very sane and sound idea.
Cheers,
Rémi
--
On 29-05-2008 08:54:48 +0200, Rémi Cardona wrote:
Marius Mauch a écrit :
So, do you think it should be enabled by default?
Does portage have a way to report which libraries it is keeping around
because of preserve-libs ? If there's an easy way to figure that out,
then enabling it by
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marius Mauch wrote:
| The purpose of this is to keep the system operational after library
| upgrades until all affected packages could be rebuilt and to simplify
| the process, not to avoid the rebuilds.
I couldn't find it mentioned in your email,
2008-05-29 08:54:48 Rémi Cardona napisał(a):
Does portage have a way to report which libraries it is keeping around
because of preserve-libs ?
portageq list_preserved_libs /
--
Arfrever Frehtes Taifersar Arahesis
signature.asc
Description: This is a digitally signed message part.
On Thu, 29 May 2008 09:28:16 +0100
Mike Auty [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marius Mauch wrote:
| The purpose of this is to keep the system operational after library
| upgrades until all affected packages could be rebuilt and to
| simplify the
As portage-2.2 is about to be unmasked into ~arch soon (there is one
weird bug to solve before) it's time to ask for some input on one of
the important new features, FEATURES=preserve-libs.
(if you're already familiar with it you can skip this paragraph)
Simply said, when this feature is enabled
On 01:13 Thu 29 May , Marius Mauch wrote:
One concern raised by some people is that it might cause old libraries
with security issues to stay on the system for eternity even though
the package was upgraded, and eventually be preferred by new builds.
I can't rule this out completely but
