3 ms·
If you want your software to work everywhere, you either need to take responsibility for making it build everywhere (yes, including old versions of Debian which
by josephg 6y ago
If you want your software to work everywhere, you either need to take responsibility for making it build everywhere (yes, including old versions of Debian which don’t support the versions of your dependencies you need) or you punt that work to someone else - in which case your software simply won’t work on lots of computers. From the perspective of an upstream maintainer, the status quo is pretty awful.
There’s a reason people are turning to docker - because the “portable executable” idea on Linux is so often broken by weird incompatibilities between libc versions or some important dependency being missing or broken from some users’ systems. Automatic package translation suffers the exact same problem - a dynamically linked binary you build on your computer often won’t run on my computer.
- drran 6y agoIf you want for your software to work everywhere, but you want to avoid compilation step, then use Perl/Python/PHP with bindings to QT/GTK. Linux has perfect backward compatibility, I still able to compile and run 70 years old app, developed on completely different OS and processor. IMHO, you think that your app/lib binary will work on all combinations of OS/processor flawlessly without recompilation, which is not true. Nobody promising that. It's by design.
- account42 6y ago> weird incompatibilities between libc versions Care to provide some examples?