On Thu, Jan 8, 2009 at 9:42 AM, Graham Murray <[email protected]> wrote: > "Mark Knecht" <[email protected]> writes: > >> Is this adding some value that I don't understand? What does it do >> that using revdep-rebuild doesn't? > > It allows the affected packages to continue working until the rebuild is > done. With the 'old' revdep-rebuild, a program using a library whose > version was incremented by an upgrade could not be started (or would > fail) until it was rebuilt to use the newer library version. With the > 'new' @preserved-rebuild, the old version of the library is not actually > removed until all the dependent packages are rebuilt. > >
Thanks Graham. That *sounds* like it should be of value. I guess then that the constant messages about doing an emerge @preserved-rebuild aren't necessarily to be followed, or at least not worried about if they fail as whatever program needs the libraries still has the old versions? - Mark
