Upgrading to <current>...

Alexvader · 12-05-2009, 02:08 PM

Hi Forum

I am planning to upgrade to Slackware64-current, yet I have two questions...

#1) In case I upgrade, wont the upgrade break some stuff that I installed via slackbuilds, and cpackages created with src2pkg due to versioning problems of libraries...?

#2) The Last part of the upgrade process is clean-system... does this remove all that does not belong to Slackware-<current> ... ?

i.e. everything that is in var/log/Packages and is not in current gets removepkg'ed and wiped out... ?

BRGDS

Alex

rworkman · 12-05-2009, 03:03 PM

Re #1, quite possibly, yes.
Re #2, yes.

Alexvader · 12-05-2009, 03:18 PM

Thks rworkman...

I guess I will hold my horses for now... :-)

BRGDS

Alex

BrZ · 12-05-2009, 04:02 PM

@Alexvader,

For your posts and applications you built, maybe you should upgrade your system by hand, cherry picking the packages and testing your programs before doing the full procedure. Personally, I never executed the 'clean-system' command as I have some stuff not shipped with Slackware. Some was really painful to build =]

zbreaker · 12-05-2009, 05:24 PM

I originally installed Slackware64-13 and then Alien Bob's multilib. After a few weeks (and a Clonezilla image backup) I decided to upgrade to -current. Been smooth sailing so far...

hitest · 12-05-2009, 06:02 PM

So you don't end up with a broken system perhaps back-up your stuff and do a clean install using Alien Bob's -current DVD made with his DVD build script.

http://connie.slackware.com/~alien/

I've used his build script, it works like a charm.

piratesmack · 12-07-2009, 10:50 AM

When you run clean-system, it gives you a list of packages to be removed and you can uncheck the ones you want to keep.

Alexvader · 12-07-2009, 11:04 AM

Hi Forum

Thkz for all your support here... :-)

I have already upgraded... but I had a full backup of the stuff I built either as source tarballs with full instructions ( everytime a src tarball "fights back" against being built, I write a detailed list of all my steps and moves to acheive a working binary install... just in case I have to "do the drill" all over again...) , and as Slackware packages, since everything for all I build i src2pkg it...

So I was kind of safe here...

Did not run clean system yet... (is it really necessary...? guess not by what I read here...)

Anyway, made a full upgrade after having blacklisted python ( need the 2.5.2 version ... ) and tested my stuff... so far so good...

I will go multilib now...

I have the licence for one Cad Package for Linux... ProEngineer Wildfire 3, and I want to run it under Slackware, but it is 32bit release...

I already know I have to blacklist some stuff to keep it multilib in case i rin slackpkg again...

I guess that packages slackbuilt or src2pkg'ed for <stable> keep valid after changing to <current>... as long as you do not allow some stuff to be upgraded... :-)

BRGDS

Alex