On Monday, March 6, 2017 at 12:13:44 AM UTC+3, Michael Stapelberg wrote:
>
>
>
> On Sun, Mar 5, 2017 at 9:14 PM, > wrote:
>
>> Hi!
>>
>> Michael, thank you very much for your reply! override_dh_auto_install
>> feature does helped eliminate Go sources from the final .deb archive.
>>
>
> …why? Ple
On Sun, Mar 5, 2017 at 9:14 PM, wrote:
> Hi!
>
> Michael, thank you very much for your reply! override_dh_auto_install
> feature does helped eliminate Go sources from the final .deb archive.
>
…why? Please describe what you did, what you expected, and what you see
instead.
>
> As for dh-golang
Hi!
Michael, thank you very much for your reply! override_dh_auto_install
feature does helped eliminate Go sources from the final .deb archive.
As for dh-golang not being for the end users -- do you know any
alternatives which are more suited for the end users for building .deb
packages?
On S
dh-golang is not maintained by the Go team, so a better place to get
support is the pkg-go-maintainers mailing list.
1. No, and given dh-golang’s scope, this won’t be added (it’s a tool for
Debian development, not for end users).
2. No. Currently, we delete the source from binary-only packages, e.
Hello!
I am trying to learn how to use debhelper infrastructure to build Debian
packages from Go code. I've install dh-golang and Go itself from
jessie-backports and all seems to work quite well. But I'd like to change
two things which don't fit well enough in my workflow.
1. Is there a way to
