Hello!
Someone could explain me why the /slackware-11.0 is receiving contant updates while the /slackware-current is out to-date?

Shouldn't be the contrary?
I really don't got it.






Take a look:

ftp://ftp.slackware.com/pub/slackwar.../ChangeLog.txt

ftp://ftp.slackware.com/pub/slackwar.../ChangeLog.txt

I have to admit, I think slackware-current is overdue, but here is the official explanation

Thu Nov 9 18:16:50 CST 2006
Q: Hey, what's the deal with -current?
A: Renovations are underway to the toolchain (gcc, glibc, binutils, etc),
and it makes little sense to update what is essentially Slackware 11.0
only to do the work all over again once the new toolchain is ready.
In addition, these things aren't going as smoothly as anticipated.
I'd like to put the NPTL version of glibc into /lib and the LinuxThreads
version into /lib/obsolete/linuxthreads (since some old binaries are
going to need them), but doing this prevents the use of a 2.4 kernel.
Perhaps it's finally time to drop support for Linux 2.4? Personally,
I'd rather not as 2.4 is more forgiving of flaky hardware and thus
tends to get better uptimes (at least on the servers I run ;-).
Comments about this issue are welcomed.
glibc-2.5 has also been having some problems with locale support here
that need to be investigated and dealt with. I'd rather base the glibc
in Slackware on an official glibc release, but using the development
repo is also something under (slight) consideration if it works better.

The updates that go into Slackware 11.0 (as well as all previous releases down to 8.1 even which received 3 updates in 2007!) are part of the usual process of keeping the versions of Slackware secure and safe to use after their initial release.
New features and packages are by tradition only added to the Slackware-current tree. So far, this development of adding or upgrading packages, and changing the way Slackware works (think of the boot process, hardware detection, network support and so on) has been an incremental, evolutionary process - the day-to-day changes that you see reflected in the ChangeLog.txt are fairly small and if things break, theya re usually fixed very fast.

Now, with the new post-slackware 11.0 development, things were due for a major reshuffle. Expect to see a lot of things changed - all of that may not be visible to the casual end user but under the hood, things change much!
Simply stated, when such a significant change happens, it is not easy to let it all come together again as a working distro ;-) When the slackware-current release is fit for the general public, Pat _will_ release his updates, and they are many!
That this is not being reflected in the ChangeLog.txt of the moment does not mean that development has slowed down or even halted. Pat Volkerding of course decides when a new slackware-current will hit the servers, but my estimate is that it can't be long.

My advice to people who use Swaret, Slapt-get and others to automatically keep their PC up to date is: please configure that program to get updates from a Slackware-11.0 mirror and not use Slackware-current! We will probably hear a lot of moaning from people otherwise, although there will be a CHANGES_AND_HINTS.TXT file like there was for Slackware-11.0 in case you need information about the upgrade.

Eric

Could this next release possible be the most significant release of slackware yet? I have used slack since 7.1 but these new changes sound very interesting.

Thanks for the update, Eric:-) I've been curious about this as well and suspected that a lot was happening behind the scenes.

From what I've read so far I expect the next Slack release to be very different from what it is now. I'm really curious to see it and to see if Pat does shift from the 2.4 kernel series to 2.6

With so many changes at the most basic level it's to be expected that packages will be slow to show up in -current. Pat doesn't like to just toss bad/broken packages out there willy nilly. That's why I trust Slack.

Other than the note in the the Changelog, do we have any info on the state of development from sources close to Pat?

Alien Bob is "close". Check out http://www.slackware.com/~alien

Eric, do you happen to know, will the support for 2.4 cease in -current, or not?

Maybe some of the most curious readers on this thread will be interested in reading this IRC-log

http://wigglit.ath.cx/slackware_botl....log.08Mar2007

Yes, questions asked about the new default kernel (2.6), modular X (yes), and the state of -current (busy busy... coming real soon to a server near you) are all answered in that IRC log.

I should add, I am running this slackware-current for a couple of weeks now, and it is only getting better ;-) It is just so rough at the edges that some major polishing still needs to be done - especially to the installer. I do have my USB/PXE installer scripts finished already.

Eric

Wow, that is great to hear! This is the information I was lacking... Thanks a lot! Now I can go back to sleep...

erklaerbaer, KleB and Alien Bob, thank you so much for the information...

It sounds like 12.0?? will need to be a clean install

I'm sure you wanted to thank Yalla-One instead of me...