First patches for Slackware 11 have arrived!

For people who use my rsync_slackware_patches.sh script to keep their local mirror of the Slackware patches up to date, you will have to download the latest version of that script because Pat V. changed patches/ChangeLog.txt into a symbolic link. My old version of the script chokes on that.
NOTE that if you use that script for mirroring the "/patches" of older releases of Slackware, you're also need to upgrade to the latest version of the script because Pat changed all patches/ChangeLog.txt files to symlinks.

Eric

Great script - thanks for that.

I am a little confused. Why did 11.0 get a patch but there are no updates to -current? I am assuming that if I "hide & watch" the updates will be posted.
Regards,
Bill

Slackware 11.0 is an official release and so it will get patches for those packages where Pat V. deems it necessary to plug security holes. A released version of Slackware will usually not get any new features added afterwards (like, new packages).

On the other hand, Slackware-current is the product of the ongoing developement process. This never sees "patches" although the same stuff that you see in slackware-11.0/patches will most certainly appear in slackware-current too, but then as updates. It is just that the new development has not yet started as far as we can see, so even if Pat had already made packages (and let's face it, slackware-current equaled slackware-11.0 until today so he probably just used the ones he added as "patches" to Slackware 11.0) he had not updated the development tree with them.
Only when you see changes appear to the ChangeLog.txt of slackware-current does the new development cycle "officially" start. Until then, there is no reason at all to use slackware-current.

Eric

Thanks for clearing up my misinformation. I guess I was confused because I haven't done a complete install since somewhere in the 9.X series. I'll start patching until the updates begin to flow.
Thanks again,
Bill