On 22 August 2017 at 01:17, Paul R. Tagliamonte <paul...@gmail.com> wrote:
> Why not use the import path I so lovingly put in the generated control > file for times like these? > That's still missing from heaps of packages, isn't it? I know someone who likes writing scripts to fix lots of golang packages at once... Cheers, mwh > On Aug 21, 2017 9:12 AM, "Balint Reczey" <balint.rec...@canonical.com> > wrote: > >> Package: dh-make-golang >> Version: 0.0~git20170703.0.5eaf198-2 >> Severity: wishlist >> >> Dead Maintainer, >> >> When looking for packaged build-dependencies the vendor's path >> (github.com/onsi/ginkgo) is converted using the default go library >> naming scheme >> (to golang-github-onsi-ginkgo-dev) which package may not exist in >> Debian but may exist under a different name >> (golang-github-ginkgo-dev). >> >> In case the build-dependency does not exist in Debian as a package >> following the >> standard go naming scheme dh-make-golang could look for it under a >> different name using the Homepage field of the packages: >> >> $ grep-dctrl -FHomepage github.com/onsi/ginkgo -sPackage \ >> /var/lib/apt/lists/*Packages | sort | uniq >> Package: golang-ginkgo-dev >> >> Cheers, >> Balint >> >> >> -- >> Balint Reczey >> Debian & Ubuntu Developer >> >> _______________________________________________ >> Pkg-go-maintainers mailing list >> pkg-go-maintain...@lists.alioth.debian.org >> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg- >> go-maintainers >> > > _______________________________________________ > Pkg-go-maintainers mailing list > pkg-go-maintain...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers >
