Slackware-current

mlangdn · 05-25-2011, 09:52 PM

-current is on the move again. Not sure if i want to jump back in again. just yet.

kgs · 05-25-2011, 10:12 PM

-current is always on the move.

And no, I wouldn't want to jump back in either. I dislike running unstable software. The only time I ran a machine on -current was when the previous stable version's kernel did not support my wifi card, and -current was very close to being "stabilized."

But it's always good to see the dev team doing what they do best. :-)

hitest · 05-25-2011, 10:13 PM

Quote:

Originally Posted by mlangdn

-current is on the move again. Not sure if i want to jump back in again. just yet.

Woot! Jump on in the water is fine.

hitest · 05-25-2011, 10:39 PM

Quote:

Originally Posted by kgs

And no, I wouldn't want to jump back in either. I dislike running unstable software.

Well prior to 13.37 being released I was running three -current boxes. I've now moved most of my boxen to 13.37, but, I have one -current box. On occasion there are some hiccups with -current, but, in my opinion it is fair and accurate to say that slackware-current is a lot more stable than the general releases of some distros I could name. So I must take exception with your characterization of slackware-current as being unstable software. That is generally not true.

escaflown · 05-25-2011, 10:57 PM

Quote:

Originally Posted by kgs

-current is always on the move.

And no, I wouldn't want to jump back in either. I dislike running unstable software. The only time I ran a machine on -current was when the previous stable version's kernel did not support my wifi card, and -current was very close to being "stabilized."

But it's always good to see the dev team doing what they do best. :-)

Perpetual -current runner: as long as you know what you're doing, I believe it's safe to run current

piratesmack · 05-25-2011, 11:49 PM

I'll probably go to current when Alien's KDE packages require it (assuming he continues to provide them)

trademark91 · 05-25-2011, 11:52 PM

i still worry about a package breaking really far down the line of a bunch of deps i built manually breaking something important. it would take forever to track down what broke and try to build that file and everything that depended on it all the way up the chain. but i havent experienced that yet so im keeping my fingers crossed...

im a daredevil.

willysr · 05-26-2011, 01:11 AM

I'm always running on -Current and everything is fine

zbreaker · 05-26-2011, 07:29 AM

I've been pretty happy with -current though I always keep one Slack install on stable. This update is a biggie...new 38 kernel...lot's of fun!

sycamorex · 05-26-2011, 07:43 AM

I usually install a stable version and shortly after that then -current on a separate partion. Soon I find myself booting -current more and more so I eventually forget about the stable system.
I think it's time to go -current

zordrak · 05-26-2011, 07:49 AM

As long as you keep a backup of a known working version/configuration - do whatever you like so long as the machine's not a production system that needs to be stable.

willysr · 05-26-2011, 08:59 AM

and also always read the Changelog before upgrading/updating to the latest batch of update

chexmix · 05-26-2011, 10:12 AM

I pretty adamantly ran -current only for a long time, with few problems I can recall ... until it finally registered with me that SlackBuilds (which I inevitably use) are for stable releases & that there is potential trouble with mixing SlackBuilds and -current.

This has especially been true for me since I have adopted a few SlackBuilds ...

manzdagratiano · 05-26-2011, 11:14 AM

I've been using -current for quite some time now. I have installed a plethora of stuff from Slackbuilds.org using sbopkg, and all was well. In the case of any trouble, you can always edit the SLACKBUILD file manually, or in the worst case scenario, use src2pkg, which is a beautiful piece of software (unless someone prefers the old way of compile-make-make install, which I liked except for the last step when there was checkinstall, and now that there is no more, I'd rather use src2pkg).

-current is SOLID.

chexmix · 05-26-2011, 11:56 AM

Quote:

Originally Posted by manzdagratiano

I've been using -current for quite some time now. I have installed a plethora of stuff from Slackbuilds.org using sbopkg, and all was well. In the case of any trouble, you can always edit the SLACKBUILD file manually, or in the worst case scenario, use src2pkg, which is a beautiful piece of software (unless someone prefers the old way of compile-make-make install, which I liked except for the last step when there was checkinstall, and now that there is no more, I'd rather use src2pkg).

-current is SOLID.

All true of course. And as someone noted above, Slackware's -current beats many distros' supposedly stable releases.

I presently have one laptop running -current and another running -stable (I use the -stable box for SlackBuild work).