Looking at Slackware64-current, the oldest package in there is linux-faqs but that package was never compiled on slackware64... I took it from the 32bit Slackware tree at the time.
The oldest compiled package in slackware64-current is pmake (created when I was recovering from surgery and thought of something to kill the boredom). Here is the top-5 oldest packages:

For 32bit -current it is a different story because it predates the 64bit OS by many years:

3 members found this post helpful.

Wow. Thanks. The oldest 32-bit packages were compiled before my first Linux installation

AFAIK ispell, amp and seejpeg in Slackware version 14.1 all date back 24 feb. 2002, the oldest being ispell.

At least that's what I see on my rsync'ed local mirror, Marcin.

PS Too late again, sorry.

1 members found this post helpful.

To stay OT, wondering when the pages in Installation help were last updated?

Maybe there is a clue: the last Slackware version to ship boot disks and root disks was Slackware 11.0, released on 02-Oct-2006

I think someone just volunteered to update the installation docs

2 members found this post helpful.

Really? I'm already running current because some stuff just got old on 14.1... Well, to be honest xfce 4.12 is my biggest reason (and I also needed some new packages for something that I really can't remember right now... turned out it wasn't that important after all).. But two years is a lot of time in our days for just doing security updates..

On the bright side, -current is actually pretty stable right now

1 members found this post helpful.

I'm running Xfce 4.12. on Slackware 14.1, with all the bells and whistles.

Cheers,

Niki

1 members found this post helpful.

Thanks for all you've done!
Learned much from your very helpful blog mate...

Cheers

+1.
We do owe Alien Bob, Robby Workman and others (sorry, names don't come to mind) many thanks for all their significant contributions to Slackware.

IIRC, rworkman is "the force" behind Xfce and many, if not most, of the updates and changes we see in the "x" directory.

Alien Bob, aka, Eric, is/was "the force" behind the 64-bit version of Slackware and the creator and maintainer of the Mulitlib system for Slackware64.

For those who don't have the time or the inclination to compile their own applications, Alien Bob's many packages makes Slackware useable for end users who would otherwise be driven to a different Linux distribution.

Just off the top of my head, Alien Bob provides,
KDE 4.14.3 for Slackware-14.1 (and for -current, before it was officially added),
Qt5,
KDE 5.x for -current,
Chromium and the flash and widevine plugins for the same,
Corefonts,
Ffmpeg,
Gst-plugins,
Icedtea-web and Rhino, which are needed for
Openjdk,
LibreOffice,
Veracrypt,
VLC,
Flash,
Wine,
Wine-pipelight,
Handbrake,
and many, many more.

As to "major changes"... well, it was version 12 before we no longer had to manually mount optical drives, and that was overdue.
It was Slackware-13 before we saw a 64-bit version and that was way overdue.
I don't recall when Networkmanager was added, but it was a welcome addition.
It was just this last April when KDE 4.14.3, was added to -current and that was way, way, way overdue.
I don't know what lies ahead, but, just my two cents worth, if someone wanted to broaden the appeal (use) of Slackware in the professional/corporate world, PAM should be included and it should have been done three or four years ago. As I said, just my two cents worth.

11 members found this post helpful.

Slackware release cycle seems to be really slow, i still love it but its a shame :/ i guess it helps maintain the stability of the system though.

Use the -Current young padawan.

As of today it is just 18 days until we celebrate the 2nd anniversary of the release of 14.1. Unless there is some major changes awaiting in the wings, the next release could well be called, 14.1a.

What would you consider a "major" change?

A lot of packages have been updated since 14.1 in -Current, so that alone is a major change. We've pushed into a new kernel series, many of the core applications in /a have been updated to new and maintained versions, Mesa has evolved to support WINE/D3D9 better, and has gained variable drivers for both the traditional Tungsten API and the Gallium API respectfully on all chipsets including Intel, and X has been updated also, plus various other components.

Changes to a version don't need to be drastic and jaw-dropping-kick-you-in-the-crotch-make-your-eyes-bulge changes. They can be subtle and simple changes that are elegant and quiet.

Well said and "subtle and simple changes" call for an incremental bump in the version number.

Why not just playfully screw with the rest of the Linux community and number the next release Slackware 42 or something?

Regards.

1 members found this post helpful.