User: Password:
|
|
Subscribe / Log in / New account

Slackware 14 released

Slackware 14 released

Posted Sep 30, 2012 0:33 UTC (Sun) by blackbelt_jones (guest, #62623)
Parent article: Slackware 14 released

I've been trying the release candidates. The xfce 4.10 is sweet, but I couldn't install KDE3 from binaries that were released for Slackware 13.0. KDE4 is not terrible, but I just can't let go. I suppose I'll have to try a compile, but for now I'll be sticking with Slackware 13.37


(Log in to post comments)

Slackware 14 released

Posted Sep 30, 2012 6:31 UTC (Sun) by Camarade_Tux (guest, #51944) [Link]

Of course you cannot install KDE 3 binaries which were made for 13.0! I remember someone on IRC trying to do that one year ago. It didn't work back then and it won't work now either.

As a general rule:

NEVER MIX BINARIES FROM DIFFERENT VERSIONS (OF SLACKWARE).

Slackware 14 released

Posted Sep 30, 2012 16:09 UTC (Sun) by blackbelt_jones (guest, #62623) [Link]

Well, it works great with 13.37

Slackware 14 released

Posted Sep 30, 2012 19:12 UTC (Sun) by Camarade_Tux (guest, #51944) [Link]

You've been very lucky.

Slackware 14 released

Posted Sep 30, 2012 16:42 UTC (Sun) by burdi01 (guest, #65371) [Link]

"NEVER MIX BINARIES FROM DIFFERENT VERSIONS (OF SLACKWARE)". *Most* of the time this rule of thumb is simply not true. You may have to carry forward some libraries, but that is all there is to it.

Actually the last KDE 3 (3.5.10) was for 12.2, and I have been carrying forward that version for quite some time. I think that missing hal will be the stumbling block for running that version for 14.0.

At the moment I run Trinity 3.5.13 on Current (which at the moment is identical to 14.0). There are some glitches, but nothing fatal.

Slackware 14 released

Posted Sep 30, 2012 18:25 UTC (Sun) by blackbelt_jones (guest, #62623) [Link]

>>Actually the last KDE 3 (3.5.10) was for 12.2,

Well, no, there's this:

http://ftp.gwdg.de/pub/linux/slackware/unsupported/kde-3....

Thanks for the tip.

Slackware 14 released

Posted Sep 30, 2012 18:45 UTC (Sun) by blackbelt_jones (guest, #62623) [Link]

I had some problems last time I tried Trinity.

(sigh) Hello, XFCE.

Slackware 14 released

Posted Sep 30, 2012 19:17 UTC (Sun) by Camarade_Tux (guest, #51944) [Link]

Differences of semantics. :-)

What we usually say is: do not mix. Of course, stuff like xlander hasn't been recompiled recently and yet it works well. But for packages that have changed, don't attempt to take one from version X of the distribution and use it on version Y. Don't attempt to do backports.

Slackware 14 released

Posted Sep 30, 2012 15:39 UTC (Sun) by geofft (subscriber, #59789) [Link]

That's true of all distros, right? Isn't that just how we decided dynamic linking on Linux is going to work?

Slackware 14 released

Posted Oct 1, 2012 14:15 UTC (Mon) by vonbrand (guest, #4458) [Link]

No. One of the (many) benefits of dynamic linking is that you can change the library (as long as the ABI remains) under the executables. Thus, a change to fix, e.g. a security problem, doesn't require rebuilding the world. If the library developer is careful, this can work for a surprisingly long range. And you can (via library versions) have several ABIs supported at the same time.

Slackware 14 released

Posted Oct 1, 2012 19:24 UTC (Mon) by zlynx (subscriber, #2285) [Link]

Unfortunately the Linux community is lucky if the developer even notes an ABI change in the change log, let alone bumps the .so version or maintain versioned symbols. (Although as someone who maintains a proprietary C++ library for Linux, I understand what a pain versioned symbols are for anything but C.)

Of course if the developer does bump the .so version, good luck getting any bug fixes back-ported into the last version.

Slackware 14 released

Posted Oct 4, 2012 0:26 UTC (Thu) by nix (subscriber, #2304) [Link]

For ABI additions, you're pretty much right (which means you can run older binaries on newer systems, but not generally vice versa). However, for ABI changes and deletions, soname compatibility is maintained pretty well for the vast majority of packages, and it is universally considered a bug if it is accidentally broken. Recently, even some of the odious old standbys like OpenSSL have come into the light. (Berkeley DB remains a frequent-breakage annoyance, but even it bumps its soname when appropriate. And often when not appropriate.)


Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds