Take the 2-minute tour ×

I have Slackware 13.1 installed on my computer, with some software that I installed via pkgtools, slackbuilds, and compiled. I want to upgrade it to Slackware-current (13.37).

Can I safely upgrade this by following UPGRADE.txt? Is this a big leap that will come problem (dependency, version conflict, etc)?

What about my additional application that I installed via slackbuilds or compiled, are there any chance that they don't compatible with the newer library version?

share|improve this question
As a sidenote: -current and 13.37 are different beasts. -current is "almost 14.0" by now, it's more akin to "the latest developer version" with all that entails, good and bad. –  Ulrich Schwarz Jul 3 '12 at 12:07
add comment

1 Answer

up vote 2 down vote accepted

If you want to do this upgrade, I'd upgrade to Slackware-13.37 first, using the hints in UPGRADE.txt, and then upgrade 13.37 to -current once that is complete. During each release cycle, several packages are added and removed, so to move from 13.37 to current in the second step, you should read the Changelog closely to see what steps you might need to take to run current.

There will likely be Slackbuilds which do not work in the latest -current, especially since there has been an upgrade to a new GCC which breaks certain build scripts. Additionally, the usual warning that SlackBuilds.org does not support -current still applied. That being said, many people run current and use SlackBuilds without much problem. For programs that you have compiled yourself, the same caveats apply.

If you follow UPGRADE.txt and Changelog notes you should have a -current system running fairly easily. It's hard to say if you will have problems with your other applications without knowing what they are, but I shouldn't think it will be a major issue.

share|improve this answer
add comment

Your Answer


