And before anyone jumps on this bandwagon: DON'T !!!!
See UnSpawn's edict when he closed the most recent systemd thread: http://www.linuxquestions.org/questi...ml#post5382514

1 members found this post helpful.

Mia Culpa, amigo. Sometimes I forget how international this group is.

"Spitting out updates like a slot machine" is pretty obviously an attempt at humor for native born English speakers however I can see how it would confuse people translating that literally into another language.
As far as being offended... no worries, appreciate the heads up, actually and will attempt to be clearer.

1 members found this post helpful.

Not everyone is comfortable running a release that isn't officially marked as stable (no matter how stable -current actually is), especially when running production equipment. Plus, managing updates on -current vs stable is much more involved (and as it is always said, people should expect breakage with -current and know how to fix it -- even if it doesn't happen often). With many of the changes in recent kernels and mesa, there are obvious graphics benefits with running a newer version (not to mention improvements in other programs included), so I understand people getting antsy for a new stable release (although, I personnally know better than to ask when).

Since I run multiple machines in my house on Slackware, I try to keep them all on the same version so I can compile software on my fast computer (server) and transfer it to my slower computers (htpc and laptop) without needing to worry about library/program differences. xbmc/kodi takes hours to compile on my htpc where it is less than a third of that on my server. Plus, I need to keep my kodi versions the same since I run a shared database (which is why I prefer to share builds, since I occasionally will build from their git). While I've done this on -current, it is much easier to do on a box that doesn't have the possibility of libraries changing all the time (think of how much 3rd party software needed to be recompiled after that big update in April).

1 members found this post helpful.

Yes. Slackware is under active development. Patrick will release Slackware 14.2 when it meets his standard of excellence.
Enjoy Slackware.

My bad too. Though I suspected you might be kidding there, I just didn't get it. Anyways good day!

Regards.

I'm interested in a new release in regards to the pending legality that now surrounds distributions being able to legally use ZFS since Debian, if I'm not mistaken, got the green light to use ZFS in a release by the legal team from the Software Freedom Law Center. New rulings like the ZFS ruling by the SFLC change the ball game and could bring some new interesting things to distributions.

I'd rather the ZFS, Wayland, or OpenRC bandwagons get rolling down the road. Much more sane discussion and productivity with those topics that have real benefits in the long term, and they can be discussed over nice cold beers very peacefully.

1 members found this post helpful.

That should not be reasons to look forward to the new release since you already know that none of ZFS, Wayland, OpenRC are going to be added.

All I have to say is

3 members found this post helpful.

Very true Eric. Maybe not immediately, maybe not ever, but still the discussion on those is tame by fair comparison and often ends more sanely. Concerning topic of "that which should not be mentioned", it think it's best, in my opinion, just don't ask... ever.

1 members found this post helpful.

I'm totally comfortable running any flavor of Slackware, 13.37, 14 or 14.1 since they all have support for security bugs and required patches. I'm like others here, able to use Slackware as a tool not a toy. I don't need the rush to latest hardware and software. Since I install Slackware on hardware that is a much as 10 years old and new as 1 year old I don't have any issues with the current applications included in 14.1 Thank you to Patrick and the great group of supporters who patch applications, build SlackBuilds and give hints on how to use the most Unix like Linux...Slackware.

1 members found this post helpful.

The new mesa in current has improved graphics a lot for me even on my old thinkpad -- in fact, some applications making use of 3D show annoying "glitches" on 14.1. In -current, that's fixed (intel graphics). The new xorg-input-evdev also has support for the IBM/Lenovo ScrollPoint mouse. Its scroll knob is properly supported now.

Those who are interested: add the following to /etc/X11/xorg.conf.d/99-scrollpoint.conf:

and voilà! scrolling should be much smoother and less erratic now.

2 members found this post helpful.

That is pretty much the same thing, slackware current is rolling. Upgraded software is (semi)regularly added to the repos beyond just bug fixes.

its rolling like a rock

1 members found this post helpful.

True, but usually rolling releases have what are called trees of software.

Stable
Current
Experimental

Arch, Funtoo, and Gentoo are rolling release distributions. They have several trees people can use, however the true rolling, resides in the Experimental branch. Current and Stable have certain guidelines that must show the package distributed has some stability within the system, and can be used with all the software regardless. Experimental just adds new packages regardless. However, Current in Slackware isn't always "Current" even with stable software in release by authors. Current in Slackware usually involves new packages, bug fixes, hot fixes, and stable releases, but not all of these are "current" packages.

Even then Rolling releases do NOT have stable branches that utilize a version control system.

-current is *not* a rolling release. Rolling, by definition, has no release versions, only snapshots. See this discussion for more details. It is discussing Ubuntu, but for the purposes of this discussion, the definition of a rolling release still applies

-current is a series of updated packages from the previous -stable version, in this case, 14.1. But there will be a release made in due time, which makes Slackware adhere to the traditional software release model.

I should note for the record that you will rarely go wrong if you install -current in a clean install; however, there is no guarantee of stability, although often (over 90% in my experience) you will experience no ill effects, but if stability is paramount, and it is for some situations, -stable is your best best.