slackware-current/source
Patrick J Volkerding 6ca133bba7 Fri Dec 25 06:10:08 UTC 2020
l/harfbuzz-2.7.3-x86_64-2.txz:  Rebuilt.
  Seems the --enable-introspection option didn't work, so rebuild with meson
  since that's probably what most of the developers do. Fixes blueman.
  Thanks to marav for the bug report.
2020-12-25 17:59:48 +01:00
..
a Fri Dec 25 00:52:08 UTC 2020 2020-12-25 08:59:52 +01:00
ap Fri Dec 25 00:52:08 UTC 2020 2020-12-25 08:59:52 +01:00
d Fri Dec 25 00:52:08 UTC 2020 2020-12-25 08:59:52 +01:00
e Sun Nov 29 20:52:56 UTC 2020 2020-11-30 08:59:53 +01:00
f Mon May 28 19:12:29 UTC 2018 2018-05-31 23:39:35 +02:00
installer Thu Dec 17 23:02:41 UTC 2020 2020-12-18 08:59:50 +01:00
k Fri Dec 25 00:52:08 UTC 2020 2020-12-25 08:59:52 +01:00
kde Fri Dec 25 00:52:08 UTC 2020 2020-12-25 08:59:52 +01:00
l Fri Dec 25 06:10:08 UTC 2020 2020-12-25 17:59:48 +01:00
n Fri Dec 25 00:52:08 UTC 2020 2020-12-25 08:59:52 +01:00
t Sat Oct 31 01:29:37 UTC 2020 2020-10-31 08:59:53 +01:00
tcl Sat May 9 20:49:43 UTC 2020 2020-05-10 08:59:54 +02:00
x Fri Dec 25 00:52:08 UTC 2020 2020-12-25 08:59:52 +01:00
xap Fri Dec 25 00:52:08 UTC 2020 2020-12-25 08:59:52 +01:00
xfce Fri Dec 25 00:52:08 UTC 2020 2020-12-25 08:59:52 +01:00
y Sun Feb 17 23:44:53 UTC 2019 2019-02-18 08:59:47 +01:00
buildlist-from-changelog.sh Thu Feb 20 04:50:54 UTC 2020 2020-02-20 17:59:49 +01:00
make_world.sh Thu Nov 22 05:56:56 UTC 2018 2018-11-22 17:59:46 +01: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