-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 26/09/13 06:51 AM, Michael Palimaka wrote: > On 26/09/2013 17:53, Michał Górny wrote: >> 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".
Enforcing consistency is much more important imo than "emerge -uDN @world" efficiency. For those users that need more efficiency they can always get it by upgrading individual packages with '--rebuild-ignore' or '--ignore-built-slot-operator-deps y' after seeing what all is going to be rebuilt via 'emerge -uDNav' To be honest, the main issue that I see keeping slot-operators from being properly used has to do with virtuals, because subslots (or full slots for that matter) do not propagate through them. But that doesn't hold back converting libs and rdeps for everything not falling to a virtual. > 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. The latter in that case was a mis-use of the ':=' on the poppler atom in *DEPEND. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (GNU/Linux) iF4EAREIAAYFAlJEQOkACgkQ2ugaI38ACPCp1QEAsSX+efIdTGRZ94EIgyYzQcSF 4TeEmFvzanp5A/6DL94BAIVnw3ayjTmOmUYevRl/Hr0cEyVv4X9T+bFnhngW6Ops =CsnH -----END PGP SIGNATURE-----
