Re: [RFC] Go (golang) packaging
On Wed, Jan 02, 2013 at 01:05:46PM +0100, Guillem Jover wrote:
> - Private dependencies, as they leak to rdeps. When a library uses
> another library privately this dependency gets linked in directly
> in all other rdeps, when that library stop depending on that
> private dependency, all rdeps need to be rebuilt.
Strictly speaking, if you're only using static libraries this is not
really true; once you've compiled something against a static library,
the static library might change in whatever way it sees fit, the
compiled binary will continue to work, with or without recompilation.
This isn't true if you're using a mix of shared and static libraries, of
> * Produces huge binaries (and packages), which use more memory that
> cannot be shared across processes (unlike shared libraries).
Also, if a significant body of code exists that uses a particular
library, this will have a significant influence on mirror archive size,
and installed size of Debian systems.
Copyshops should do vouchers. So that next time some bureaucracy requires you
to mail a form in triplicate, you can mail it just once, add a voucher, and
save on postage.