| |||||||||||||
The Grumpy Editor's guide to (some) development distributionsThe Grumpy Editor's guide to (some) development distributionsPosted Nov 9, 2007 0:42 UTC (Fri) by zlynx (subscriber, #2285)In reply to: The Grumpy Editor's guide to (some) development distributions by evgeny Parent article: The Grumpy Editor's guide to (some) development distributions
> Today you installed, configured it, everything works fine. Tomorrow you do "emerge world" and - oops - libexpat now version 2.0.something instead of yesterday's 1.95.something. Both are stable. But the library sonames are different, so now you have to revdep-rebuild all the related packages (which are dozens, both system- and desktop-level), and until the process successfully finishes (if it does), your box is literally unusable. There are some tricks you can do with CONFIG_PROTECT to force portage to save old versions of library files.
(Log in to post comments)
The Grumpy Editor's guide to (some) development distributions Posted Nov 12, 2007 16:21 UTC (Mon) by evgeny (guest, #774) [Link] > There are some tricks you can do with CONFIG_PROTECT to force portage to save old versions of library files. CONFIG_PROTECT is about protecting _config_ files...
The Grumpy Editor's guide to (some) development distributions Posted Nov 12, 2007 17:30 UTC (Mon) by zlynx (subscriber, #2285) [Link] > CONFIG_PROTECT is about protecting _config_ files... That does not mean you can not (ab)use it for protecting library files. Or without the double negative... CONFIG_PROTECT does work to protect non-config files.
|
|||||||||||||