Slackware-current

NoStressHQ · 11-08-2011, 10:03 AM

Another tip using current with slackpkg, don't forget to issue first:

Code:

# slackpkg install-new

THEN

Code:

# slackpkg upgrade-all

And finally

Code:

# slackpkg clean-system

...

The two firsts are because some package upgrade might rely on "new" packages (although it might not be a problem most of the time).
The last one, must be done carefully in the sense that you might want to keep all your 'custom' installed packages (through SBOs...) BUT some package might become deprecated, and the 'clean-system' will allow you to remove those packages...

Welcome to -current !

Cheers

Garry.

NightSky · 11-08-2011, 05:29 PM

FYI if you don't want to install ie. kde, its base, or lib you have to blacklist them so when you

Code:

# slackpkg install-new

you don't install what you don't want

Cheers

What if you did not blacklist all the kernel lines in /etc/slackpk/blacklist and you already upgraded to the last kernel? Can you just build a custom kernel and then blacklist kernel related lines, so long as everything is working properly? Thank you

dc_eros · 11-08-2011, 05:33 PM

I've been using Slackware current at home and at work for more than a year. During those early days, I always end up with a broken video driver, games requiring perl not running, etc.

But for now, I carefully read the ChangeLog.txt before applying updates and usually visit this forum to find if there are issues with current. So far so good.

Doesn't actually affect my work.

ottavio · 11-10-2011, 07:47 AM

slackpkg is ok if you want to keep a stable release up to date or install single packages but I don't advise using slackpkg to catch up with current without looking at the changelog because it might give you headaches.