Re: Two questions about packaging: go-mtpfs as a binary package and removing documentation files

[Julian Gilbey <julian@d-and-j.net>]

On Thu, Aug 23, 2018 at 01:10:18AM +0800, Shengjing Zhu wrote:
> On Wed, Aug 22, 2018 at 11:54 PM Julian Gilbey <julian@d-and-j.net> wrote:
> >
> > Hello,
> >
> > Two quick questions.
> >
> > (1) go-mtpfs currently produces the executable by that name.  But it
> > still ships the Go source code, which doesn't make much sense.  Would
> > it be OK to convert this to a binary-only package?
> 
> IMHO, yes. The source code should be in -dev package when needed(other
> packages Build-Depends on it).
> The recommend way to prevent installing the source code, is to
> override `dh_auto_install` with `dh_auto_install -- --no-source`.

Thanks - that seems straightforward enough.

> > (2) golang-github-hanwen-go-fuse installs AUTHORS and README.md into
> > /usr/share/gocode/src, but surely it shouldn't?  (They are installed
> > into /usr/share/doc.)  What is the recommended way to prevent this
> > from happening?
> 
> The reason is that you set `export DH_GOLANG_INSTALL_ALL := 1` in
> rules. Then you need to filter the files yourself.

Doh!  I'd forgotten I'd put that there....  I'll switch to
DH_GOLANG_INSTALL_EXTRA.

Thanks again!

   Julian