Re: [RFC] Go (golang) packaging
On Tue, Jan 1, 2013 at 9:44 PM, Michael Stapelberg wrote:
> Any feedback is appreciated. Please read the wiki page before you
> comment, it contains more rationale than this email. Thanks.
Since golang apparently doesn't support dynamic linking, every package
built against a golang library will have to include an appropriate
Built-Using header. You will probably also want a lintian test for
this to autoreject anything without this header.
Upstream should switch to using the GNU triplet instead of linux_arm,
which is clearly not unique enough.
Is it possible to:
Support dynamic linking? That would avoid the whole rebuild-the-world
thing that statically-linked languages have.
Not require the full source code for libraries? C and other libraries
only require the interface headers.