I think that's an opinionated preference: the risk of having obsolete stale man pages is considerable, especially for fast-moving packages which often is the case for Go packages. This is a subjective maintainer decision, so up to you. Although it seems a bit weird to now have a mostly help2man-generated static file shipped, which begs the question if the file is the preferred form of making modifications to.
The best is indeed if you can convince upstream to accept to ship a man page, then you don't need a Debian-specific hack. I've had success with several packages for this. Commit 4a19ff16968ee87c112c615288c9e749a61ffeaa touches on several non-debian/ files, could you back those changes out? Only the debian/patches/ file is necessary. I get other build errors now. I'm happy to continue the review later, but don't let that stop others from helping out too. dpkg-source: info: using source format '3.0 (quilt)' dpkg-source: info: building siso using existing ./siso_1.5.12+ds.orig.tar.gz dpkg-source: info: using patch list from debian/patches/series dpkg-source: info: local changes detected, the modified files are: siso/execute/localexec/rusage_unix.go dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/siso_1.5.12+ds-1.diff.ajUfTv dpkg-source: hint: make sure the version in debian/changelog matches the unpacked source tree /Simon Juan <[email protected]> writes: > Thanks Guillem! Very clarifying. Changed to a minimal manpage. > > About contributing it upstream to a project like chromium, what are > your thoughts? We can try, but I am not hopeful of the acceptance. So > far in the packages that I am contributing just created it for the > Debian package. > > Continuing! As before, more changes may come as I verify full builds > for all architectures. > > Juan > -------- Original Message -------- > On Wednesday, 05/06/26 at 19:47 Guillem Jover <[email protected]> wrote: > Hi! > > Using help2man for compiled programs breaks cross-compilation. And > adapting the packaging to support help2man and cross-building is IMO > not worth the supposed gain of using help2man, because it requires > doing a native and a host build to be able to run the program. > > A static man page is superior in any possible way, also because just > using the output from --help tends to be not very useful anyway (except > for providing that output on the sites like manpages.debian.org). > > Using help2man as a starting template to further fill in a static man > page seems like a good use for that tool though. > > Thanks, > Guillem > >
signature.asc
Description: PGP signature
