Index of /slackware/slackware-current/source

Name	Last modified	Size

Parent Directory		-
CHECKSUMS.md5	2018-10-17 21:48	449K
CHECKSUMS.md5.asc	2018-10-17 21:48	163
FILE_LIST	2018-10-17 21:48	635K
MANIFEST.bz2	2018-10-17 21:48	15M
README.TXT	2006-10-02 06:40	1.3K
a/	2018-10-01 19:28	-
ap/	2018-09-07 00:56	-
buildlist-from-chang..>	2018-04-23 21:29	12K
d/	2018-09-28 01:57	-
e/	2018-02-03 03:50	-
f/	2018-02-27 07:13	-
installer/	2018-10-11 00:22	-
k/	2018-10-13 20:23	-
kde/	2018-06-18 04:22	-
kdei/	2018-01-31 06:38	-
l/	2018-09-21 05:08	-
make_world.sh	2018-05-08 04:32	13K
n/	2018-10-04 20:44	-
t/	2018-02-24 21:15	-
tcl/	2018-02-01 04:10	-
x/	2018-10-10 20:16	-
xap/	2018-07-30 23:05	-
xfce/	2018-06-25 22:55	-
y/	2018-02-04 20:07	-


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