who think 3 years ..is fast development cycle ? ... no one...and more important , the cycle is not ends on the horizont.

you confused under receiving updated libs ... and receive new release , is not the same....you can do a million of updates per day , arround 10 years , and no end the cycle...then cause you receive a million updates per day is fast cycle ? .. no , thats only fast updates.

cycle ends ..when stable 14.2 pass to 15.0 , for the moment all days got updates for -current ... but not 15 in the horizont ...then after 3 years thats is slow. (for me)

1 members found this post helpful.

???

-current has Python 3. It also has Python 2 to support the legacy software that still needs it.

1 members found this post helpful.

Ok , i see people are fanatic here .. this is the list , of new things ... remember , some are added ,forced to another one lib/package

I think ,after 3 years this is poor new things added , ITS MY OPINION.

some curl ..and grep commands can open eyes.

If remove from the list , the video drivers and extra aspell ... and some added to replace old apps ..what have after 3 years ?

Im not discuss more here, is lost time...3 seconds and 1 console command can open eyes of people.


rust --> forced by firefox
python3 --> forced by intel-gpu-tools
openssl1 --> to mantain old compatibility
mlocate --> replacement for locate
lhasa --> if im not bas to replace dhasa
rxvt-unicode --> to replace normal version not suporting utf8
mypaint-brushes --> required bu gimp

other "added", are a "RENAMED" ,projects ... im not see too new and exciting things here.

really added by decision are easytag , krb5 ffmpeg ..and some old apps replacement.

For me , as i say , one more time. is a slow cycle.

I really don't understand the panic and wailing.

Today nature called. I found myself sitting for a long many minutes. I knew the instant the bowels started moving that I would be humbled in place. I was going nowhere for a long while. Each time I thought I was done the bowels laughed. An evil laugh. The aroma was offensive. Not enjoyable at all.

There are other times when the bowels immediately tell me that the experience will be enjoyable. Down right gratifying. Pleasing. No evil laugh.

Slackware is developed with much thought and earnest. Just about everything gets done right and just about everything comes out right. Much like a peaceful bowel movement with three rest notches and a Dairy Queen tip.

Rapid release is just one long messy stinky sh-t. The result is about the same as my experience today when nature called.

Eat your veggies. Stay away from the junk food.

Edit: I should not post past my bedtime! The moral of the story is be patient. Slackware 15 will be a great release, much better than any rapid release distro. Eat your veggies refers to Slackware. Healthy! Junk food refers to rapid release. Not healthy!

3 members found this post helpful.

Hmm. At one time, I thought I could make the most disturbing comment in this forum without breaking the rules.

I have given up on that minor quest and bow to the master, @upnort.

5 members found this post helpful.

What if current stays...current? Like a continual release, sort of thing?

Development has been fast paced, the "development cycle" has been long and slow. Those are two completely different things. You did not state "cycle" in your first post like you did here, and how many packages are added does not speak to how fast development is moving. It is how many packages have changed during that development.

There's been over 6000 packages added, upgraded, or removed in -current (grep -e "Added\." -e "Removed\." -e "Upgraded\." slackware64-current/ChangeLog.txt | wc -l) in 3.5 years. Right now, we're at 1308 days, which if we take the 6116 packages that have changed, we have an average of 4.67 packages that are somehow changed every day. If we do that same command with 14.2 (and remove any patches so we're just tracking development of 14.2 while it was still "-current" -- piping the results to grep -v patches then pipe it to wc -l), we have 2523 package changes in 969 days. That's an average of 2.60 package changes a day. So -current development of 15.0 is almost double the pace of 14.2's development.

Even if you don't want to count the mass rebuild (which I'd argue was a major development change in Slackware and should be counted) and remove all 1200ish packages at the time that were rebuilt that day, that would still put -current at 3.76 package changes per day.

I think everyone can agree that the development cycle of 15.0 has been slow, but the development of 15.0 itself has been moving at possibly record-breaking speeds for Slackware (I'm too lazy to go check the rest of the development cycles).

NOTE: I bolded the word "think" above because I want to reiterate that I'm not putting words in everyone's mouth like was insinuated from one of my earlier posts, possibly in another thread. It is a guess that I have that there isn't anyone out there who thinks this is a normal development cycle for Slackware.

4 members found this post helpful.

Actually, dovecot and postfix was a nice move.

3 members found this post helpful.

One day it will be 15; for while at least, until the development begins anew.

1 members found this post helpful.

Because people have different habits and minds. Here, my main machine gets the updates and stores them in a local repo where they are merged with things I build myself. Then the other machines get their updates from this repo. This speed-up updates and gets me a chance to see if something needs attention before locally spreading new things. And this is really straightforward to do because in -stable you almost never have new dependency. I don't care of having the latest software, I just want it to put the bytes where they are meant to be. That's why -stable really makes me happy: once I have installed the package base it needs, I am almost done with a machine.

With -current, this will just turn a nightmare, because I'll have to evaluate carefully the new packages and have to add a mechanism (aka "dependency resolving for the poor man") to tell the other machines they need this or this one according to their particular setups (I don't speak of the removals, because it's a minor issue on the short term) or go full install everywhere, even on the FTP, which is stupid (therefore it would probably stay in -stable, and instead of one branch, I'd have to track two).

3 members found this post helpful.

One reason I decided to move to Slackware was its stability. I have used rolling releases in the past (Arch, Debian Testing) but I don't really like them. Like a lot of old people, I'm a bit paranoid about things going wrong during updates. And that's why I don't want to use Slackware Testing

5 members found this post helpful.

I ran Arch for a time, but, tired of the breakage. I've been running -current exclusively for a few years and find it for the most part to be very stable.
Slackware 15.0 will be worth the wait.

I used Arch for about 6 months and went screaming back to Slackware. My new computer needs a lot of the hardware support current has, so was leery about Current. Current is so much different than Arch, it's not even comparable. For one, you don't have everyone and their cousin patching everything six ways to Sunday, so things actually compile and run on Slackware. Also, updates don't break everything.

Spoken like a true fangoil.

#wink-wink #humor #teasing