[SOLVED] Slackware-current

qlands · 02-07-2011, 05:24 AM

Hi,

I am fairly new to Slackware. Now I have 13.1 64bits. I see that some users update to Slackware-current. For what I can see, current would allow you to have update packages like KDE among others. My questions are: Which are the advantages and disadvantages of Slackware-current? Would you recommend it for a intermediate user? How I update my Slackware to current?

Thanks,
Carlos

D1ver · 02-07-2011, 05:48 AM

Quote:

Originally Posted by qlands

Hi,

I am fairly new to Slackware. Now I have 13.1 64bits. I see that some users update to Slackware-current. For what I can see, current would allow you to have update packages like KDE among others. My questions are: Which are the advantages and disadvantages of Slackware-current? Would you recommend it for a intermediate user? How I update my Slackware to current?

Thanks,
Carlos

-current is the development branch of slackware. Updates go in here first for testing before they are passed along to the stable releases. Things can break in current and your expected to fix/test/report problems and issues that you have yourself.

It may not be the best for intermediate/beginner users. I'm currently a bit of a noob and am running current on my personal desktop machine (it has nothing mission critical on it) and it seems very stable.

The advantage is that your at the bleeding edge of the distribution with the latest versions of all your packages. You can upgrade by uncommenting a 'current' server in your
'/usr/etc/mirrors' file and doing

Code:

slackpkg update
slackpkg install-new
slackpkg upgrade-all

You'll want to read the change logs and other documentation assosiated with current before you upgrade though to make sure there isn't any tricks your missing.

bgeddy · 02-07-2011, 05:58 AM

See GazL's response in this other thread.

Quote:

How I update my Slackware to current?

No offense meant here but if you have to ask that perhaps you shouldn't really run current.

onebuck · 02-07-2011, 07:30 AM

Hi,

Quote:

Originally Posted by qlands

Hi,

I am fairly new to Slackware. Now I have 13.1 64bits. I see that some users update to Slackware-current. For what I can see, current would allow you to have update packages like KDE among others. My questions are: Which are the advantages and disadvantages of Slackware-current? Would you recommend it for a intermediate user? How I update my Slackware to current?

Thanks,
Carlos

Quote:

excerpt from CURRENT.WARNING;
Welcome to Slackware-current!

*** Please note that you must already be ***
*** running a 2.6.x kernel before ***
*** upgrading to Slackware-current! ***
*** ***
*** upgradepkg glibc-solibs before other ***
*** packages. Take care not to miss new ***
*** packages that were split from old ***
*** ones: upgradepkg --install-new is ***
*** (as always) the safest approach. ***

Slackware-current is a snapshot of the active Slackware development tree.
It is intended to give developers (and other Linux gurus) a chance to test
out the latest packages for Slackware. The feedback we get will allow us
to make the next stable release better than ever.

See the ChangeLog.txt for a list of changes in Slackware-current.

Please note that the code in this directory is unstable. It might be
inconsistent about which version of the Linux kernel is required, could be
incomplete because it's in the process of being uploaded, or might not work
for other reasons. In most cases, we know about these things and are working
to correct them, but still -- feel free to point out the bugs.

Production use is AT YOUR OWN RISK and is not recommended.

I suggest as a Slackware user, either running 'stable' or '-current' one should always read the text files available. You will always have information that will aid one to make good decisions.

2handband · 02-07-2011, 08:48 AM

If you want stability, stick with the stable version of Slackware (currently 13.1). If you want bleeding-edge software, run Arch. Only run Slackware -current if you're interested in helping with development by testing and reporting problems.

hitest · 02-07-2011, 09:35 AM

Quote:

Originally Posted by 2handband

If you want bleeding-edge software, run Arch.

No offense to Arch users, but, I prefer Slackware-current over Arch. I find Arch to be *too bleeding edge* for my tastes. Slackware-current is far more stable by comparison. I was an Arch user.

To the original poster. If you do choose to run slackware-current please be prepared to roll up your sleeves and trouble-shoot your PC if things go awry. I've found -current to be very stable, but, things on occasion do break. Support is freely given for the stable releases of Slackware. You are expected to help solve issues in -current and report anomalies if they occur.

2handband · 02-07-2011, 11:34 AM

Quote:

Originally Posted by hitest

No offense to Arch users, but, I prefer Slackware-current over Arch. I find Arch to be *too bleeding edge* for my tastes. Slackware-current is far more stable by comparison. I was an Arch user.

To the original poster. If you do choose to run slackware-current please be prepared to roll up your sleeves and trouble-shoot your PC if things go awry. I've found -current to be very stable, but, things on occasion do break. Support is freely given for the stable releases of Slackware. You are expected to help solve issues in -current and report anomalies if they occur.

I do both; I run Arch on my desktop (and it actually runs pretty damn well) and Slackware stable everywhere else.

hitest · 02-07-2011, 11:40 AM

Quote:

Originally Posted by 2handband

I do both; I run Arch on my desktop (and it actually runs pretty damn well) and Slackware stable everywhere else.

Yes. Arch is a fine distro indeed!

It was a pleasure to meet and interact with the good people from the Arch community.