[pkg-go] Usage of Built-Using for dev packages

[Alexandre Viau]

Hello team,

During my NM process, I was asked to justify the use of Built-Using on
golang dev packages.

In the past, I was asked to add it to my golang dev packages by a
sponsor from the team.

I don't think that the intent of the Built-Using field described in the
Debian policy fits with this kind of use. It says that "the source
packages of those other packages are a required part of the complete
source".  This is not the case for source code packages.

However, I can see that it can be useful for archiving purposes. Its
easier to see in what condition the package was built.

If we choose that the Built-Using field does not make sense for source
packages, we should reflect this in dh-make-golang.

see:
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-built-using

Have I missed anything? thoughts?

Thanks,

-- 
Alexandre Viau
alexandre at alexandreviau.net

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-go-maintainers/attachments/20150910/366b23fb/attachment.sig>