slackware-current/source
Patrick J Volkerding 8ff4f2f51a Fri May 25 23:29:36 UTC 2018
patches/packages/glibc-zoneinfo-2018e-noarch-2_slack14.1.txz:  Rebuilt.
  Handle removal of US/Pacific-New timezone. If we see that the machine is
  using this, it will be automatically switched to US/Pacific.
2018-05-31 15:18:32 -07:00
..
a Slackware 14.1 2018-05-31 22:57:36 +02:00
ap Slackware 14.1 2018-05-31 22:57:36 +02:00
d Slackware 14.1 2018-05-31 22:57:36 +02:00
e/emacs Slackware 14.1 2018-05-31 22:57:36 +02:00
f Slackware 13.0 2018-05-31 22:41:17 +02:00
installer Slackware 14.1 2018-05-31 22:57:36 +02:00
k Slackware 14.1 2018-05-31 22:57:36 +02:00
kde Slackware 14.1 2018-05-31 22:57:36 +02:00
kdei Slackware 14.1 2018-05-31 22:57:36 +02:00
l Fri May 25 23:29:36 UTC 2018 2018-05-31 15:18:32 -07:00
n Slackware 14.1 2018-05-31 22:57:36 +02:00
t Slackware 14.1 2018-05-31 22:57:36 +02:00
tcl Slackware 14.1 2018-05-31 22:57:36 +02:00
x Slackware 14.1 2018-05-31 22:57:36 +02:00
xap Slackware 14.1 2018-05-31 22:57:36 +02:00
xfce Slackware 14.1 2018-05-31 22:57:36 +02:00
y/bsd-games Slackware 14.0 2018-05-31 22:51:55 +02:00
README.TXT Slackware 14.0 2018-05-31 22:51:55 +02:00

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