mirror of
git://slackware.nl/current.git
synced 2024-11-16 07:48:02 +01:00
9f99889c0c
Happy 25th anniversary to the Slackware 1.00 release! When the original announcement went out on Usenet, I believe it had a UTC timestamp which has led to some confusion over whether the anniversary falls on the 16th (which was the date when I made the post) or on the 17th (which is when most people first saw it)... but really, what's the difference? We can celebrate on both days as far as I'm concerned. Thanks for sticking with the project all these years. Glad I was able to help. :) Here's a link to the 1.00 announcement: http://www.slackware.com/announce/1.0.php And here's a nice article that was posted on opensource.com: https://opensource.com/article/18/7/stackware-turns-25 a/kernel-firmware-20180717_8d69bab-noarch-1.txz: Upgraded. l/pulseaudio-12.2-x86_64-1.txz: Upgraded. n/gnutls-3.6.3-x86_64-1.txz: Upgraded. n/mutt-1.10.1-x86_64-1.txz: Upgraded. This update fixes bugs and security issues. Upstream strongly recommends that all IMAP and POP users upgrade as soon as possible. (* Security fix *) |
||
|---|---|---|
| .. | ||
| a | ||
| ap | ||
| d | ||
| e | ||
| f | ||
| installer | ||
| k | ||
| kde | ||
| kdei | ||
| l | ||
| n | ||
| t | ||
| tcl | ||
| x | ||
| xap | ||
| xfce | ||
| y | ||
| buildlist-from-changelog.sh | ||
| make_world.sh | ||
| README.TXT | ||
This is the source used for Slackware. To look for a particular bit of source (let's say for 'cp'), first you would look for the full path: fuzzy:~# which cp /bin/cp Then, you grep for the package it came from. Note that the leading '/' is removed: fuzzy:~# grep bin/cp /var/log/packages/* /var/log/packages/cpio-2.4.2.91-i386-1:bin/cpio /var/log/packages/fileutils-4.1-i386-2:bin/cp /var/log/packages/gcc-2.95.3-i386-2:usr/bin/cpp /var/log/packages/gnome-applets-1.4.0.5-i386-1:usr/bin/cpumemusage_applet From this, you can see that 'cp' came from the fileutils-4.1-i386-2 package. The source will be found in a corresponding subdirectory. In this case, that would be ./a/bin. Don't be fooled into thinking that the _bin.tar.gz in this directory is the package with the source code -- anything starting with '_' is just a framework package full of empty files with the correct permissions and ownerships for the completed package to use. Many of these packages now have scripts that untar, patch, and compile the source automatically. These are the 'SlackBuild' scripts. Moving back to the example above, you can figure out which package the bin/cp source came from by examining the SlackBuild script. Have fun! --- Patrick J. Volkerding volkerdi@slackware.com