On Mon, Feb 15, 2016 at 08:41:18AM +0100, Michael Stapelberg wrote: > I’m having some trouble understanding what exactly the bug is that you’re > reporting here.
Hello Michael, Thanks for the quick response! > With regards to -dev dependencies ending up in Build-Depends _and_ Depends, > that > was fixed in dh-make-golang already, see > https://github.com/Debian/dh-make-golang/commit/1f158eb4ab41ba72a8ba9386864a10a9d9bf2ded Ah, thanks, I hadn't noticed that. I'll update my package accordingly. > With regards to putting source and binaries into different packages, I don’t > understand why dh-golang would be involved at all? dh_install can be used for > this, > see https://anonscm.debian.org/cgit/collab-maint/codesearch.git/tree/debian > for > an example. > Can you please clarify if anything remains to be done, or whether that > addresses > the issue? I realise that, thanks. It's more that by default, dh-golang includes the Go source code in all golang-* packages, whether they are program or library packages, and I'm unclear why this is a sensible thing to do. I'm perfectly happy to use dh_install or the like to modify its behaviour for this individual case, but it seems to me that there is an argument for modifying the dh-make-golang + dh-golang system to offer three possibilities, something like the following: (1) -type=library Behaviour as at present: creates a -dev package including the Go source code and doesn't compile anything. (2) -type=program Behaviour different from present: creates a binary package only, with the compiled Go program, excluding all Go source code. (3) -type=combined (or some other appropriate name) Compiles a Go program to produce a binary package containing only the compiled Go program; also creates a corresponding -dev package providing the Go source code. What are your thoughts on this? Best wishes, Julian
