On Tue, 28 May 2013 16:43:10 +0200 David Carlos Manuelda <stormb...@gmail.com> wrote:
> I posted a bug about that along with a suggestion, despite sometimes I do not > explain myself correctly (I am very sorry): bug #471590 > > Many packages are bundling its own libraries rather than link against system > ones, and there is a bug tracker for that (bug #251464) > [...] > What I propose for example, is a very good and simple approach: to have an > option in portage's make.conf, something like that (the name may change): > > 1.- USE_SYSTEM_LIBRARIES="cairo sqlite XXX" > 2.- USE_SYSTEM_LIBRARIES="* -cairo" > 3.- USE_SYSTEM_LIBRARIES="*" I don't think we should do it like this. Bundling libraries is a pathological case. In general, we should work on fixing this and getting rid of bundled libraries. In that general case, the flags are not required. The remaining cases usually involve libraries that are somehow forked or otherwise deviated from upstream. For example, the sqlite within Mozilla products has a few braindead features enabled that are not really suitable for system-wide use. In those cases, every library needs to be considered separately and the concept of local flag matches that. Making it anyhow a global matter would suggest that each bundled sqlite is equal and each reason for bundling is exact the same. That said, I don't see why a user would want to choose to have some libraries bundled, and others not in a global manner. -- Best regards, Michał Górny
signature.asc
Description: PGP signature
