On 26/09/2013 17:53, Michał Górny wrote:
Dnia 2013-09-26, o godz. 15:15:38
Patrick Lauer <[email protected]> napisał(a):
Thus I suggest declaring a policy:
""
Any library bump that would trigger revdep-rebuild should be done with
the affected library package.mask'ed until all its consumers have been
properly bumped to subslot-aware versions.
""
(The unmasking of the library then triggers a "migration" to happy
portage updates that don't need human supervision)
How do we handle packages which install multiple libraries? I'm afraid
forcing such a policy and/or hurrying developers to adapt will only
cause more of poppler-like issues to occur.
There isn't a 100% perfect solution currently, and I agree that hurrying
people will simply move us from "not enough rebuilds" to "too many
rebuilds".
Poppler was a great example of what can go wrong. Apart from people
being forced to rebuild packages that link only against one of the
stable interfaces, I even saw rebuilds forced for packages that didn't
even link against the libraries.
