Is Slackware dying?
There's only been 1 release in almost 5 years.
|
Um, wat? Last release was 2 years ago per slackware.com and there is plenty activity in --current for 32 and 64bit.
|
This looks like a troll...
Check the official ChangeLogs (http://www.slackware.com/changelog/) and you will notice that it's not dying. |
Quote:
|
Quote:
|
Obviously its not dying but I have to say after the whole fiasco with the store and Pat's general comments about how to monetize it so he can eat I thought some more might happen. I understand there are challenges updating the legacy site etc. Given the situation taking a week away from Slackware 15 development to stand up a wordpress site would have made sense to me. At the very least post something to the existing front page; just so the latest content there does not say 2016. Anyone who does follow Slackware Closely does not know to check change logs.
Seriously a post dated 2018 like "Slackware 15 On the Way" expect {blah blah changes include {some already updated major libs etc}}". Would help a lot. |
hey, if you live under a bridge and eats goats then what do you expect! ;)
I was more concerned a few years ago when visible progress on current actually stopped for several months. I don't know what Pat's reasons are for not having cut a release for so long, 'current' has certainly felt "good enough" at serveral points to me, but I guess he has his reasons. To my mind anything over 18 months is too long between releases, but my thoughts on the subject don't count for anything. |
Ah yes, it's the annual "Is <Slackware> <Gentoo> <dying> <dead>?" thread! :rolleyes:
|
Quote:
|
Quote:
|
Quote:
|
Darth_Vader alternate account detected.
|
Quote:
|
Quote:
This is purely a trollpost. 800 posts and hardly any reputation says a lot about this poster's contributions to the forums. Go on, OP, rail one at me. I've been dealing with people like you online for years. Give it your best. |
Threads like this come up every once in awhile. It is understandable, considering how close Pat keeps everything to the chest, the fact that the release cycle has lengthened over the last few releases, and some outdated information on the website. When asked in good faith by someone just trying to get information, the responses don't look like this:
Quote:
Quote:
Quote:
Quote:
|
Quote:
From my point of view, all you can state today is that it took 2 1/2 years to release 14.2. You cannot state anything regarding the next release because it would lead to very fragile/unstable results (and it would be denying the hard work done by the maintainers to make the next release happen). Let's see:
|
Quote:
|
Quote:
|
Quote:
:hattip: |
Quote:
|
|
Quote:
|
Quote:
|
Quote:
|
Quote:
Still, on the minuscule off-chance that you are incapable of getting the rather large hints shunted your way... An OS is looked on as 'dead' or 'dying' when it stops receiving updates for a prolonged period. Slackware receives frequent updates. In fact, the most recent updates for 14.2 were just on Saturday [and that goes for the third party Slackbuilds too]. Latest updates for -current were on Monday. You can see this all at the following link: http://www.slackware.com/changelog/ but if you've been using Slackware for years surely you must know where to find this information. The wait between 14.1 and 14.2 was slightly longer [2y 7m], thus far, than between 14.2 and 15.0 [currently 2y 5m]. Your posts are rude and unnecessary, but you know this. You have been told repeatedly, yet you persist since you either enjoy it or you have a very insecure nature [or a mixture of both]. Additionally, you have already been provided with the information you requested. This is why your posts are looked on as trolling. A word of advice - people will be much more likely to work with you [or even for you], if they like you. You're not currying much favour here. |
Quote:
Besides, that wasn't the point you made in your OP, which was about the number of releases over so many years, not the amount of development done. |
Have you donated to Slackware recently? If you were worried about Slackware "dying", then why not donate to it?
Your whole question was "There's only been 1 release in almost 5 years.", which implies that it means that it's dead, because of that. A simple search of this forum would have found you this post. Where not only does Slackware's main developer want to continue developing Slackware, but where you had a significant outpouring of support for Slackware from even people that rarely post here. I had no issues opening Slackware's website, and therefore could have downloaded it. Even the date on the home page of it's website is 2016-07-01, which is just over 2 years ago - not 5 years ago. I'd think if Slackware was actually "dead", it's website would probably be offline, along with any download servers for it, and more to the point: PV would have the decency to inform it's users of that beforehand. |
Quote:
|
Quote:
|
Quote:
The magnitude of the version numbers doesn't have any significance. There's a post where Pat clarifies that. |
Actually, quietguy47, it is YOU who is dying not Slackware, first because this thread is "wilting on the vine" and most importantly because you have obviously bought into the fals equation "NEW == IMPROVED". You do realize wheels are still round and haven't been updated in some 10,000 years, right? When one gets the fundamentals right, all that's left to do is just minor refinements.
|
Quote:
|
Quote:
|
Calm down, folks. The OP has won 2/3 of his reputation points answering a similar question. So to hopefully give him a definitive answer:
Quote:
|
The OP is probably only frustrated that Slackware 15 was not released yet. Maybe he/she wants to put some pressure on the release date... The Logic is - if the new version will not be released immediately = Slackware is dying. And this should scare us and the developers :) nice try!
To be fair, I also had the impression that the release was very close already 6 months ago (due to some other threads...). So I can understand the reason for this question (if it was meant sincerely .. of course). But I can also remember about discussions of Plasma 5 integration. I think some open questions regarding this were not decided yet (but it's possible I've just missed them...). Anyway. There is no point to urge the new release. In fact premature releases are always causing more troubles opposed to benefits. It's ready when it's ready.. All I know is, Slackware 14.2 is perfectly satisfying my needs ;) |
Quote:
|
https://www.linuxquestions.org/quest...ml#post5451830
Quote:
Quote:
Quote:
|
I actually find it really interesting that it started this thread in the middle of the night (assuming its location is accurate), was very aggressive for one and a half hours, and then suddenly stopped.
|
Feeling the nostalgia... reminds me of the similar threads in between the 13.37, 14.0 and 14.1 releases (and I note that old gem of updating the website got a mention as well).
|
Quote:
|
Quote:
|
Quote:
|
Quote:
:D |
[[digression begins]]
Quote:
There can be a difference between pre-Slackware appearance and post-initiation usage. Coming from Windows 7 via Ubuntu and Debian like I did, learning Slackware was a real feat. I don't have a *nix background and I had to really want to learn it in order to succeed with it. It took a long while for the learning curve to level out and to get into a place whereby I was fully comfortable [I recall this as being about four months into usage, as opposed to just two weeks with Debian]. I don't think I would have learned as much as I did without dasein's help. To the uninitiated, and even to some seasoned *nixers, Slackware and its manual dependency management can seem unappealing. It's far easier to go for something like apt which will take care of that work for you. It's only when one gets stuck in and gets one's hands dirty with Slackware that one sees that it's really not that bad. Now I can do most things in Slackware with my eyes closed; in January of this year I was struggling to comprehend the basics. I suppose, to fully qualify the quote, I should mention the whole thing: Quote:
Indeed, this "ease-of-use" is subjective to who the user is. Some *nixers might find it easy, some would find it horrendously hard. For me, the quote has technical and personal sides to it. I can see it from the point of view of a pre-Slackware user, an ongoing Slackware user, and it also has personal associations. You're the only one who's ever mentioned it and that's kind of interesting, since, from my time lurking on DUF, and my scant reading of your blog, I'd always put the two of you on similar levels of intellectualism [though different levels of experience]. [[digression ends]] |
lol... a long post always slows the drama :)
|
quietguy47, swearing and personal attacks aren't acceptable here at LQ. Please contact me if you'd like your posting privileges reinstated.
--jeremy |
Netcraft confirms it.
|
Is Slackware dying?
@Lysander666
I must fully disagree with your statement. I started to use Slackware quite long time ago as my first Linux distribution. I learned (I intended to). Several years later, I tried other distributions. Very difficult to do things on my own, automatic stuff making unwanted things and so on : in one word, hell. Slackware needs learning, true. Thankfully, Slackware is easy to learn : basically, rtfm. |
Quote:
Quote:
|
Quote:
|
All times are GMT -5. The time now is 02:14 AM. |