Thursday, March 22, 2007

Start Breaking Again

After more than 5 months of development and trial and error, finally Patrick Volkerding has decided to publicize the -current development again to the developers and other Slackware users who intended to seek for the next Slackware release (aiming for Slackware 12.0, but it will be officially called 11.1 for now).

As stated in the Changelog, dated Thu Nov 9 18:16:50 CST 2006, Patrick Volkerding already said that there will be a major renovations on the toolchain and it's true. If you see the -current Changelog, you will see lots of packages addition, removal, and upgrade. There are also some split up packages to make next Slackware release more modular (mostly from Xorg package. There are almost 300 new packages in x directory for the new Xorg 7.2 package only).

From the Changelog, it's most likely that the next Slackware release will be based on 2.6.x kernel only and it will be based on the latest stable kernel, but for now, Patrick still uses 2.6.18.8 version with SMP feature as the standard kernel. This is good news, as for the last 5 months, Slackware only update it's package for security vulnerabilities and it's considered outdated by some people, but NOT anymore. By using Slackware-current, you will get most of the latest version of each application available in default Slackware installation, like KDE 3.5.6, Xorg 7.2, GnuPG 2.0.3, XFCE 4.4.0, GIMP 2.2.13, CUPS 1.2.8, and many more.

PLEASE PLEASE READ the WARNING and CHANGES_AND_HINT note before you started to upgrade your Slackware version to -current or it may broke your system.

Yesterday, i started to list all new packages from -current and i started to download them all (slowly) and today, i will have them finished and start planning to upgrade to -current as it still have a chance to broke my system. When the upgrade finishes, i will start using -current as i did in the past.

No comments:

Post a Comment