Re: Best way to limit that -dev package does not have too many source files?
On 02/05/25 5:01 am, Otto Kekäläinen wrote:
> In https://salsa.debian.org/go-team/packages/usql/-/merge_requests/2 I
> am planning to introduce alongside the binary `usql` package also a
> `golang-github-xo-usql-dev` that can be used by other Go packages to
> build with this usql as a dependency.
Are there other go packages that use it *and* are suitable for Debian?
I could find only a handful when I did a github codesearch and unsure how useful
they are.
It may not be worth spending (un-necessary) cycles here if we don't anticipate
another package really using it.
> The main change is:
> override_dh_auto_install:
> dh_auto_install -- --no-source
No, don't do it. This will remove the usql binary from installation.
If you want both lib and binpkg, remove dh_auto_install override altogether.
> However, this ends up introducing a massive amount of unrelated files
> that are not really needed for the source package in terms of what is
> a build dependency.
>
> What are the recommended techniques to limit what files go into the
> source package?
>
> Use *.install files to allowlist files?
This is what I'd do, and have done in the past.
> Write a customized override_dh_auto_install ?
No, avoid complicating d/rules.
> If I define a very long DH_GOLANG_EXCLUDES it is going to affect the
> whole build, not just what files are copied into the -dev package,
> right?
Yeah, but there's no harm in trying it out.
Reply to: