Very sorry for the late reply.

I am not a skilled deb packager, and although I have checked some documentation and understand that deb packaging is not complicated, I still have some questions.

The most common linux distribution I use is ArchLinux, because it is updated on a rolling basis, so most users have the latest glibc version, for which users don't run into the problem of mismatched libc versions that golang depends on when updating nali.

For Debian/Ubuntu, users installing deb packages from the distribution repository will not encounter the problem of not finding the matching version of libc, but if I release a nali deb compiled under ubuntu 22.04, users running older versions of debian will most likely encounter the problem I mentioned.

It is not clear to me that there is an appropriate solution to this problem. And I don't see any benefit in packaging a deb package for a program like nali that only requires a single executable, I prefer to provide an automated install script or even integrate self-upgrading in nali.

https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=nali-go-bin https://github.com/makedeb/makedeb will do the job.

tl;dr: makedeb use PKGBUILD to build the deb. but only a bit of difference. https://docs.makedeb.org/makedeb/differences-from-makepkg/

为什么我不能启动它？Debian/Ubuntu 两者都不行，
wget https://github.com/zu1k/nali/releases/download/v0.8.0/nali-linux-386-v0.8.0.gz