slackware-current/source
Patrick J Volkerding 7bd3e8d27d Thu Apr 2 06:07:52 UTC 2020
a/hwdata-0.334-noarch-1.txz:  Upgraded.
a/kernel-generic-5.4.29-x86_64-1.txz:  Upgraded.
a/kernel-huge-5.4.29-x86_64-1.txz:  Upgraded.
a/kernel-modules-5.4.29-x86_64-1.txz:  Upgraded.
a/pkgtools-15.0-noarch-32.txz:  Rebuilt.
  installpkg: handle the uninstall script packaged as /install/douninst.sh.
  removepkg: add --skip-douninst option to skip running the uninstall script.
    Save removed douninst.sh in /var/log/pkgtools/removed_uninstall_scripts.
ap/groff-1.22.4-x86_64-2.txz:  Rebuilt.
  Fixed docdir. Thanks to Xsane.
d/gcc-9.3.0-x86_64-2.txz:  Rebuilt.
d/gcc-brig-9.3.0-x86_64-2.txz:  Rebuilt.
d/gcc-g++-9.3.0-x86_64-2.txz:  Rebuilt.
d/gcc-gdc-9.3.0-x86_64-2.txz:  Rebuilt.
d/gcc-gfortran-9.3.0-x86_64-2.txz:  Rebuilt.
  Patched a compiler bug concerning assumed-shape vs. deferred-shape arrays.
  Thanks to Lockywolf.
d/gcc-gnat-9.3.0-x86_64-2.txz:  Rebuilt.
d/gcc-go-9.3.0-x86_64-2.txz:  Rebuilt.
d/gcc-objc-9.3.0-x86_64-2.txz:  Rebuilt.
d/kernel-headers-5.4.29-x86-1.txz:  Upgraded.
d/ruby-2.7.1-x86_64-1.txz:  Upgraded.
  This update fixes security issues:
  Unsafe Object Creation Vulnerability in JSON (Additional fix).
  Heap exposure vulnerability in the socket library.
  For more information, see:
    https://www.ruby-lang.org/en/news/2020/03/19/json-dos-cve-2020-10663/
    https://www.ruby-lang.org/en/news/2020/03/31/heap-exposure-in-socket-cve-2020-10933/
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10663
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10933
  (* Security fix *)
k/kernel-source-5.4.29-noarch-1.txz:  Upgraded.
l/graphite2-1.3.14-x86_64-1.txz:  Upgraded.
l/librsvg-2.48.2-x86_64-1.txz:  Upgraded.
l/utf8proc-2.5.0-x86_64-1.txz:  Upgraded.
x/libva-2.7.0-x86_64-1.txz:  Upgraded.
x/libva-utils-2.7.1-x86_64-1.txz:  Upgraded.
isolinux/initrd.img:  Rebuilt.
kernels/*:  Upgraded.
usb-and-pxe-installers/usbboot.img:  Rebuilt.
2020-04-02 10:41:33 +02:00
..
a Thu Apr 2 06:07:52 UTC 2020 2020-04-02 10:41:33 +02:00
ap Thu Apr 2 06:07:52 UTC 2020 2020-04-02 10:41:33 +02:00
d Thu Apr 2 06:07:52 UTC 2020 2020-04-02 10:41:33 +02:00
e Wed Mar 11 19:54:51 UTC 2020 2020-03-12 08:59:49 +01:00
f Mon May 28 19:12:29 UTC 2018 2018-05-31 23:39:35 +02:00
installer Tue Mar 31 19:01:17 UTC 2020 2020-04-01 08:59:49 +02:00
k Thu Apr 2 06:07:52 UTC 2020 2020-04-02 10:41:33 +02:00
kde Fri Feb 7 22:32:38 UTC 2020 2020-02-08 08:59:48 +01:00
kdei Mon Sep 30 21:08:32 UTC 2019 2019-10-01 08:59:50 +02:00
l Sat Mar 28 05:48:42 UTC 2020 2020-03-28 17:59:48 +01:00
n Tue Mar 31 19:01:17 UTC 2020 2020-04-01 08:59:49 +02:00
t Mon Oct 7 04:41:29 UTC 2019 2019-10-07 17:59:47 +02:00
tcl Fri Nov 22 22:09:33 UTC 2019 2019-11-23 08:59:50 +01:00
x Thu Apr 2 06:07:52 UTC 2020 2020-04-02 10:41:33 +02:00
xap Sat Mar 28 05:48:42 UTC 2020 2020-03-28 17:59:48 +01:00
xfce Wed Mar 25 22:53:06 UTC 2020 2020-03-26 08:59:49 +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