On 21 Jul 2016, at 8:13 AM, Michael Hudson-Doyle <michael.hud...@canonical.com> 
> On 21 July 2016 at 07:39, Erick Cardona <erick0zcr....@gmail.com> wrote:
>> Hi Tim and thanks!
>> I'm just using a random upstream repository(github) and trying to package it
>> using the Debian tools. Actually dh-make-golang does all the magic and now
>> I'm able to create the .deb with the binaries and sources in it. I don't
>> know why yesterday it wasn't including the binaries in the .deb package, but
>> now is working like a charm. Today I was messing it with cowbuilder and
>> pbuilder stuff and it works. I'll take a closer look on how those tools work
>> under the hood.
>> Question: If some projects have their dependencies in the vendor dir, why
>> dh-make-golang skip those? Does Debian packages never ship the deps in that
>> way?
> It is against debian policy:
> https://www.debian.org/doc/debian-policy/ch-source.html#s-embeddedfiles

Right - it's highly preferred that vendored dependencies are unbundled from the
upstream and added as Build-Dependencies to the package.  Unfortunately this
can be a lot of work depending on the number of dependencies and nested
dependencies.  For a small package it's usually not a problem.

I haven't figured out what the best way is to create an upstream source 
file that doesn't contain the vendored source though.  For packages with 
(as opposed to snapshots of the master branch) you can use Files-Excluded
in debian/copyright and then uscan can download and repack the upstream
source.  Not sure what the best idea for git snapshot packages is yet.


> Cheers,
> mwh

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

Pkg-go-maintainers mailing list

Reply via email to