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

[Michael Stapelberg]

I agree that setting Built-Using on the -dev packages does not make
sense as long as they don’t contain binaries. golang-gogoprotobuf-dev
is an example where the -dev package does contain binaries.

As the vast majority of -dev packages does not actually contain
binaries, I’m happy to accept a pull request for dh-make-golang which
only adds Built-Using to programs (vs. libraries).

On Thu, Sep 10, 2015 at 11:09 PM, Alexandre Viau
<alexandre at alexandreviau.net> wrote:
> 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
>
>
> _______________________________________________
> Pkg-go-maintainers mailing list
> Pkg-go-maintainers at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers



-- 
Best regards,
Michael