Index of /slackware/slackware-current/source

Icon  Name                        Last modified      Size  Description
[   ] CHECKSUMS.md5 20-May-2019 23:12 456K [TXT] CHECKSUMS.md5.asc 20-May-2019 23:12 163 [   ] FILE_LIST 20-May-2019 23:12 643K [   ] MANIFEST.bz2 20-May-2019 23:12 16M [TXT] README.TXT 02-Oct-2006 06:40 1.3K [DIR] a/ 16-Mar-2019 21:25 - [DIR] ap/ 05-May-2019 20:48 - [TXT] 23-Apr-2018 21:29 12K [DIR] d/ 15-May-2019 21:08 - [DIR] e/ 03-Feb-2018 03:50 - [DIR] f/ 27-Feb-2018 07:13 - [DIR] installer/ 03-Mar-2019 21:17 - [DIR] k/ 17-May-2019 01:17 - [DIR] kde/ 18-Jun-2018 04:22 - [DIR] kdei/ 31-Jan-2018 06:38 - [DIR] l/ 04-May-2019 00:25 - [TXT] 20-Nov-2018 04:08 14K [DIR] n/ 22-Apr-2019 21:40 - [DIR] t/ 24-Feb-2018 21:15 - [DIR] tcl/ 01-Feb-2018 04:10 - [DIR] x/ 10-May-2019 21:41 - [DIR] xap/ 20-May-2019 22:35 - [DIR] xfce/ 07-Dec-2018 05:35 - [DIR] y/ 17-Feb-2019 23:31 -

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