<div dir="auto">Why not use the import path I so lovingly put in the generated control file for times like these?</div><div class="gmail_extra"><br><div class="gmail_quote">On Aug 21, 2017 9:12 AM, "Balint Reczey" <<a href="mailto:balint.reczey@canonical.com">balint.reczey@canonical.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Package: dh-make-golang<br>
Version: 0.0~git20170703.0.5eaf198-2<br>
Severity: wishlist<br>
<br>
Dead Maintainer,<br>
<br>
When looking for packaged build-dependencies the vendor's path<br>
(<a href="http://github.com/onsi/ginkgo" rel="noreferrer" target="_blank">github.com/onsi/ginkgo</a>) is converted using the default go library<br>
naming scheme<br>
(to golang-github-onsi-ginkgo-dev) which package may not exist in<br>
Debian but may exist under a different name<br>
(golang-github-ginkgo-dev).<br>
<br>
In case the build-dependency does not exist in Debian as a package following the<br>
standard go naming scheme dh-make-golang could look for it under a<br>
different name using the Homepage field of the packages:<br>
<br>
$ grep-dctrl -FHomepage <a href="http://github.com/onsi/ginkgo" rel="noreferrer" target="_blank">github.com/onsi/ginkgo</a> -sPackage \<br>
 /var/lib/apt/lists/*Packages | sort | uniq<br>
Package: golang-ginkgo-dev<br>
<br>
Cheers,<br>
Balint<br>
<br>
<br>
--<br>
Balint Reczey<br>
Debian & Ubuntu Developer<br>
<br>
______________________________<wbr>_________________<br>
Pkg-go-maintainers mailing list<br>
<a href="mailto:Pkg-go-maintainers@lists.alioth.debian.org">Pkg-go-maintainers@lists.<wbr>alioth.debian.org</a><br>
<a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers" rel="noreferrer" target="_blank">http://lists.alioth.debian.<wbr>org/cgi-bin/mailman/listinfo/<wbr>pkg-go-maintainers</a><br>
</blockquote></div></div>