Re:AppImage: Linux apps that run anywhere
by probonopd on Saturday February 27, 2016 @12:11PM
(#11187670)
Yes, except that you might want to be a bit more selective in which parts you use from the base system and which parts you want to bundle - some people might not want to have e.g. glibc in each app bundle. This is where it starts to become a little more complicated than the above, see https://github.com/probonopd/AppImageKit/wiki/Creating-AppIm...
[ Parent
| on HN ]
Re:AppImage: Linux apps that run anywhere
by lukaslalinsky on Saturday February 27, 2016 @03:19PM
(#11188296)
If you don't have glibc in each app bundle, it won't run everywhere. Different distros have different versions of glibc and it's very easy to end up in a situation where you use some symbol that's not defined in the system one.
Re:AppImage: Linux apps that run anywhere
by probonopd on Saturday February 27, 2016 @04:05PM
(#11188489)
Which is why you want to build on a system that is using an older version of glibc than the systems you want to run your software on. Assuming that glibc does't break backward compatibility, which it really shouldn't (and in practice, rarely ever did). Or use https://github.com/probonopd/AppImageKit/tree/master/LibcWra...
Re:AppImage: Linux apps that run anywhere
by inopinatus on Saturday February 27, 2016 @08:07PM
(#11189270)
This makes a mockery of shared libraries. The technical debt will accrue and run unfathomably deep. Security failures due to currency issues are simply the most obvious. The insoluble mystery bugs of mismatched dependencies will plague application developers that choose this distribution strategy.
Re:AppImage: Linux apps that run anywhere
by _hyn3 on Saturday February 27, 2016 @08:54PM
(#11189395)
Yay for hyperbole ;)
Shared libraries are most useful when matched within a specific distribution's package/version chain.
Tying a third-party distributed package to a given shared library, on the other hand, is less helpful than just supplying the expected, tested, and supported library upfront and still let knowledgeable operators do what they will on their chosen platform.
No technical debt is accrued if the libs are truly interchangeable anyway, but especially if they are not, this stands a better shot at fixing it.
Re:AppImage: Linux apps that run anywhere
by inopinatus on Saturday February 27, 2016 @10:03PM
(#11189624)
Your suggestion amounts to advocacy of tight coupling, which massively dilutes the long-term benefit of shared libraries and leads developers under pressure of expediency into a tangled thicket of anti-patterns. This is an illustration of how technical debt is accrued, and I've seen it umpteen times, never to the good.