Re: Building and using shared libraries using gccgo
* Adam Borowski:
> If there is a bug in library A, if you use static linking, you need to
> rebuild every single library B that uses A, then rebuild every C that
> uses B, then finally every single package in the archive that uses any
> of these libraries.
But wouldn't it be great if all the people wishing for something that
combines the strengths of Debian's and Gentoo's idea of software
packaging for years finally got the system they wanted as a side effect
of automating such rebuilds?