Index of /slackware/slackware-current/source

Icon  Name                    Last modified      Size  Description
[   ] CHECKSUMS.md5 20-Jan-2018 17:28 428K [TXT] CHECKSUMS.md5.asc 20-Jan-2018 17:28 163 [   ] FILE_LIST 20-Jan-2018 17:28 607K [   ] MANIFEST.bz2 20-Jan-2018 17:28 14M [TXT] README.TXT 02-Oct-2006 06:40 1.3K [DIR] a/ 12-Jan-2018 22:32 - [DIR] ap/ 19-Jan-2018 00:55 - [DIR] d/ 20-Jan-2018 04:51 - [DIR] e/ 16-Mar-2010 05:13 - [DIR] f/ 16-Mar-2009 22:18 - [DIR] installer/ 28-Jul-2017 08:21 - [DIR] k/ 17-Jan-2018 22:10 - [DIR] kde/ 27-Aug-2017 18:31 - [DIR] kdei/ 17-Jan-2016 03:17 - [DIR] l/ 17-Jan-2018 02:39 - [DIR] n/ 17-Jan-2018 05:06 - [DIR] t/ 29-Sep-2017 23:51 - [DIR] tcl/ 02-Mar-2016 21:56 - [DIR] x/ 02-Jan-2018 23:24 - [DIR] xap/ 12-Jan-2018 20:09 - [DIR] xfce/ 19-Dec-2017 21:34 - [DIR] y/ 12-May-2010 06:10 -

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