3 ms·
Yes. If you've never had a clashing Debian package build before, you've not been paying attention. I've made it my mission in life to try to get people more awa
by salawat 5y ago
Yes. If you've never had a clashing Debian package build before, you've not been paying attention. I've made it my mission in life to try to get people more aware of linkers, and the fact that when you build something the one way it works on your system it doesn't mean it will work that way on someone else's.
- eqvinox 5y agoI've never had a clashing Debian package build before, and I build quite a few Debian packages. Some for a wider audience and some for my own use. All packages that leave the confines of my own systems are built the "correct" way, in a clean minimal chroot with sbuild/schroot/cowbuilder. The docs on how to set that up are pretty good, and after you've done it once it's pretty easy to repeat for extra target distros (e.g. older Debian, Ubuntu.) What would you point out to me as part of your mission? [Just to be clear, a package is a package for a particular target distro. There's no such thing as "a .deb for software XYZ". Only "a buster .deb for software XYZ", or "a bullseye .deb for software XYZ", etc.]