3 ms·
I also like now "single file deployment" is considered a feature. It makes it easier for people without proper packaging and distribution tools. Of course these
by kevincox 4y ago
I also like now "single file deployment" is considered a feature. It makes it easier for people without proper packaging and distribution tools. Of course these people without packing and distribution tools will now have a hard time finding out everywhere they have copied these binaries to.
- LaGrange 4y agopackageblabla-1.2.3.deb is a single file.
- Beltalowda 4y agoThat 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.
- WesolyKubeczek 4y agoThe thing about "single file deployment" is that it shouldn't have external requirements, otherwise it's not a single file deployment anymore.
- kelnos 4y ago... 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".
- WesolyKubeczek 4y agoI think both grandparent you’re referring to and its parent are lost in the woods.
- LaGrange 4y agoOh 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.