From 9664bee729d487bcc0a0bc35859f8e13d5421c75 Mon Sep 17 00:00:00 2001 From: Patrick J Volkerding Date: Wed, 26 Sep 2012 01:10:42 +0000 Subject: Slackware 14.0 Wed Sep 26 01:10:42 UTC 2012 Slackware 14.0 x86_64 stable is released! We're perfectionists here at Slackware, so this release has been a long time a-brewing. But we think you'll agree that it was worth the wait. Slackware 14.0 combines modern components, ease of use, and flexible configuration... our "KISS" philosophy demands it. The ISOs are off to be replicated, a 6 CD-ROM 32-bit set and a dual-sided 32-bit/64-bit x86/x86_64 DVD. Please consider supporting the Slackware project by picking up a copy from store.slackware.com. We're taking pre-orders now, and offer a discount if you sign up for a subscription. Thanks to everyone who helped make this happen. The Slackware team, the upstream developers, and (of course) the awesome Slackware user community. Have fun! :-) --- source/README.TXT | 36 ++++++++++++++++++++++++++++++++++++ 1 file changed, 36 insertions(+) create mode 100644 source/README.TXT (limited to 'source/README.TXT') diff --git a/source/README.TXT b/source/README.TXT new file mode 100644 index 000000000..404c6de02 --- /dev/null +++ b/source/README.TXT @@ -0,0 +1,36 @@ + +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 -- cgit v1.2.3