slackware-current/source
Patrick J Volkerding 22d153f9e2 Wed Aug 1 22:38:53 UTC 2018
ap/man-db-2.8.4-x86_64-1.txz:  Upgraded.
d/gdb-8.1.1-x86_64-1.txz:  Upgraded.
d/python-pip-18.0-x86_64-1.txz:  Upgraded.
d/python-setuptools-40.0.0-x86_64-1.txz:  Upgraded.
d/python3-3.6.6-x86_64-1.txz:  Upgraded.
l/libpcap-1.9.0-x86_64-1.txz:  Upgraded.
l/pango-1.42.3-x86_64-1.txz:  Upgraded.
x/libdrm-2.4.93-x86_64-1.txz:  Upgraded.
xap/blueman-2.0.6-x86_64-1.txz:  Upgraded.
  This update fixes an issue where blueman-mechanism did not enforce the
  polkit action 'org.blueman.network.setup' for which a polkit policy is
  shipped. This meant that any user with access to the D-Bus system bus was
  able to access the related API without authentication. The result was an
  unspecified impact on the networking stack.
  Thanks to Matthias Gerstner for discovering this issue.
  (* Security fix *)
testing/packages/glibc-2.28-x86_64-1.txz:  Added.
  These packages are in /testing pending FTBFS analysis. They seem to work
  fine here, but with a few header file deprecations and some other
  possible API changes and incompatibilities (see the NEWS file), I expect
  there will be some changes required to various packages. Feel free to
  test them out though. Because of changes to the way glibc is built and
  installed that started with the glibc-2.27 packages, you can upgrade to
  these packages and also (if you wish) downgrade back to glibc-2.27 using
  upgradepkg.
testing/packages/glibc-i18n-2.28-x86_64-1.txz:  Added.
testing/packages/glibc-profile-2.28-x86_64-1.txz:  Added.
testing/packages/glibc-solibs-2.28-x86_64-1.txz:  Added.
2018-08-02 09:00:35 +02:00
..
a Wed Jul 25 03:50:17 UTC 2018 2018-07-25 13:47:10 +02:00
ap Wed Aug 1 22:38:53 UTC 2018 2018-08-02 09:00:35 +02:00
d Wed Aug 1 22:38:53 UTC 2018 2018-08-02 09:00:35 +02:00
e Mon May 28 19:12:29 UTC 2018 2018-05-31 23:39:35 +02:00
f Mon May 28 19:12:29 UTC 2018 2018-05-31 23:39:35 +02:00
installer Wed Jul 25 03:50:17 UTC 2018 2018-07-25 13:47:10 +02:00
k Sun Jul 29 08:27:12 UTC 2018 2018-07-29 21:00:41 +02:00
kde Fri Jul 20 23:16:32 UTC 2018 2018-07-21 09:00:35 +02:00
kdei Mon May 28 19:12:29 UTC 2018 2018-05-31 23:39:35 +02:00
l Wed Aug 1 22:38:53 UTC 2018 2018-08-02 09:00:35 +02:00
n Fri Jul 27 21:01:22 UTC 2018 2018-07-28 09:00:34 +02:00
t Fri Jul 20 23:16:32 UTC 2018 2018-07-21 09:00:35 +02:00
tcl Mon May 28 19:12:29 UTC 2018 2018-05-31 23:39:35 +02:00
x Wed Jul 25 03:50:17 UTC 2018 2018-07-25 13:47:10 +02:00
xap Wed Aug 1 22:38:53 UTC 2018 2018-08-02 09:00:35 +02:00
xfce Fri Jul 20 23:16:32 UTC 2018 2018-07-21 09:00:35 +02:00
y Mon May 28 19:12:29 UTC 2018 2018-05-31 23:39:35 +02:00
buildlist-from-changelog.sh Mon May 28 19:12:29 UTC 2018 2018-05-31 23:39:35 +02:00
make_world.sh Mon May 28 19:12:29 UTC 2018 2018-05-31 23:39:35 +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