Upgrading Slackware 13.1 to Slackware-current, is it a big leap

slackwareupgrade

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?

Best Answer

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.

Related Solutions

Linux – Can’t get the ‘-o remount’ option on an NFS share to work in Slackware 13.1

This doesn't exactly answer your question, but I'd advise against using rsnapshot over NFS. You are negating the primary benefit of rsync which is the ability to transfer a small amount of data over the network to detect large portions of identical data. Rsync is designed to run over ssh where it can invoke an rsync server of the other side of the connection and communicate with it via it's own optimized protocol that uses a rolling checksum to identify identical data. When rsync is run over NFS and it thinks the file might be different due to timestamps or size, it must download the entire file over NFS even if it's only a small change since it has no way of querying the remote side for checksums across the data.

Linux – Fail to install perf on slackware 13.1

Finally I solved this problem by just comment out the following line in Makefile

#ifndef NO_LIBPERL
#PERL_EMBED_LDOPTS = `perl -MExtUtils::Embed -e ldopts 2>/dev/null`
#PERL_EMBED_CCOPTS = `perl -MExtUtils::Embed -e ccopts 2>/dev/null`
#endif

It looked like MExtUtils::Embed generate wrong LDFLAGS for libperl I also found that slackware perl package only provide the static lib libperl.a

Best Answer

Related Solutions

Linux – Can’t get the ‘-o remount’ option on an NFS share to work in Slackware 13.1

Linux – Fail to install perf on slackware 13.1

Related Question