That will only work on Debian. And that "single file" requires also the libfoo-1.5.deb file (must be >=1.5, not 1.4 and not higher than 2.0!) etc.

The thing about "single file deployment" is that it shouldn't have external requirements, otherwise it's not a single file deployment anymore.

... which is why the parent is (IMO correctly) claiming that the grandparent's assertion is incorrect that a Debian package is a "single file deployment".

I think both grandparent you’re referring to and its parent are lost in the woods.

Oh no, no I'm not, and the point of the joke was that a deb is as much of a single file as your compiled go thing. It's... well, it's a single file, it's a single artifact.

And yes, it has dependencies! So does your go file, I'm afraid.