Index of /pub/linux/slackware/slackware-11.0/source

Icon  Name                    Last modified      Size  Description
[DIR] Parent Directory - [   ] CHECKSUMS.md5 23-Feb-2007 15:55 181K [TXT] CHECKSUMS.md5.asc 23-Feb-2007 15:55 189 [   ] FILE_LIST 23-Feb-2007 15:54 254K [   ] MANIFEST.bz2 23-Feb-2007 15:54 4.0M [DIR] a/ 01-Oct-2006 09:05 - [DIR] ap/ 20-Sep-2006 15:09 - [DIR] d/ 18-Sep-2006 17:32 - [DIR] e/ 12-Sep-2006 11:39 - [DIR] f/ 08-Sep-2003 11:18 - [DIR] k/ 01-Sep-2006 16:48 - [DIR] kde/ 25-Sep-2006 11:35 - [DIR] kdei/ 03-Aug-2006 04:30 - [DIR] l/ 30-Sep-2006 12:55 - [DIR] n/ 01-Oct-2006 10:07 - [DIR] rootdisks/ 30-Aug-2002 07:10 - [DIR] t/ 15-Aug-2006 10:34 - [DIR] tcl/ 31-Jul-2006 17:58 - [DIR] x/ 21-Sep-2006 18:56 - [DIR] xap/ 23-Sep-2006 18:25 - [DIR] y/ 09-Sep-2006 07:06 -

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

Then, you grep for the package it came from. Note that the leading '/'
is removed:

fuzzy:~# grep bin/cp /var/log/packages/*

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