kdev-python in KDevelop 5.6.0

Sven Brauch mail at svenbrauch.de
Wed Oct 7 17:50:54 BST 2020


Hi,

On 2020-10-06 12:34, Francis Herne wrote:
> Someone pointed me athttps://appimage-builder.readthedocs.io/en/latest/
> index.html , which removes the need for building on ancient distro releases
> altogether

I doubt that. There is a very real effect of building on the old distro: 
you build against an old glibc binary interface, which depends on an old 
kernel binary interface. glibc is guaranteed backwards compatible, but 
not forward compatible.

  * You obviously cannot ship the kernel with the AppImage.
  * For this reason, you cannot ship glibc either, because a new glibc
    might use interfaces of the kernel that don't exist yet on the
    user's older machine.
  * Thus, all your userspace libraries must not use any of the new glibc
    functionality. The only way to guarantee that I know of is to build
    against the old interface.

This problem isn't going away without a lot of effort from a lot of 
parties, I think. It isn't solvable by just shipping the right set of 
libraries, you actually need builds of the libraries that fulfill this 
condition.

Greetings!


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20201007/98e73e86/attachment.htm>


More information about the KDevelop-devel mailing list