slackware-current/source
Patrick J Volkerding 2c20c6847e Tue Jun 12 05:02:45 UTC 2018
a/kernel-firmware-20180606_d114732-noarch-1.txz:  Upgraded.
a/kernel-generic-4.14.49-x86_64-1.txz:  Upgraded.
a/kernel-huge-4.14.49-x86_64-1.txz:  Upgraded.
a/kernel-modules-4.14.49-x86_64-1.txz:  Upgraded.
a/libcgroup-0.41-x86_64-4.txz:  Rebuilt.
  Apply all post 0.41 patches from git, including one for an infinite loop
  bug that causes 100% CPU usage on one core. Thanks to chris.willing.
a/pkgtools-15.0-noarch-17.txz:  Rebuilt.
  installpkg: Use terse mode if TERSE=0 is set in the environment (this already
  works for removepkg and upgradepkg). This allows using terse mode in other
  tools that use the pkgtools (such as slackpkg with: TERSE=0 slackpkg).
  Thanks to Xsane.
ap/hplip-3.18.6-x86_64-1.txz:  Upgraded.
d/kernel-headers-4.14.49-x86-1.txz:  Upgraded.
k/kernel-source-4.14.49-noarch-1.txz:  Upgraded.
   GPIO_AMDPT n -> m (thanks to walecha)
   NFSD_V3_ACL n -> y (thanks to Jonathan Woithe)
   NFS_V3_ACL n -> y (thanks to Jonathan Woithe)
   NFS_V4_2 n -> y
  +NFSD_V2_ACL y
  +NFS_ACL_SUPPORT y
  +NFS_V4_SECURITY_LABEL y
l/LibRaw-0.18.12-x86_64-1.txz:  Upgraded.
  This update fixes bugs and security issues, including:
  parse_qt: possible integer overflow
  reject broken/crafted NOKIARAW files
  recover read position if TIFF/EXIF tag is too long
  possible infinite loop in parse_minolta()
  possible stack overrun in X3F parser
  out of bounds read in X3F parser
  For more information, see:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-13735
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14265
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10528
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10529
  (* Security fix *)
l/dconf-0.26.1-x86_64-3.txz:  Rebuilt.
  Eliminate install script noise.
l/dconf-editor-3.26.2-x86_64-3.txz:  Rebuilt.
  Eliminate install script noise.
n/iproute2-4.17.0-x86_64-1.txz:  Upgraded.
x/wqy-zenhei-font-ttf-0.8.38_1-noarch-7.txz:  Rebuilt.
  Try to avoid overriding other font choices unless lang = zh-cn or zh-sg.
x/xkbcomp-1.4.2-x86_64-1.txz:  Upgraded.
isolinux/initrd.img:  Rebuilt.
kernels/*:  Upgraded.
usb-and-pxe-installers/usbboot.img:  Rebuilt.
2018-06-12 20:58:07 +02:00
..
a Tue Jun 12 05:02:45 UTC 2018 2018-06-12 20:58:07 +02:00
ap Sat Jun 9 16:57:58 UTC 2018 2018-06-10 08:58:04 +02:00
d Wed Jun 6 22:19:01 UTC 2018 2018-06-07 08:58:09 +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 Tue Jun 12 05:02:45 UTC 2018 2018-06-12 20:58:07 +02:00
k Tue Jun 12 05:02:45 UTC 2018 2018-06-12 20:58:07 +02:00
kde Sun Jun 3 05:14:12 UTC 2018 2018-06-03 14:58:00 +02:00
kdei Mon May 28 19:12:29 UTC 2018 2018-05-31 23:39:35 +02:00
l Tue Jun 12 05:02:45 UTC 2018 2018-06-12 20:58:07 +02:00
n Tue Jun 12 05:02:45 UTC 2018 2018-06-12 20:58:07 +02:00
t Mon May 28 19:12:29 UTC 2018 2018-05-31 23:39:35 +02:00
tcl Mon May 28 19:12:29 UTC 2018 2018-05-31 23:39:35 +02:00
x Tue Jun 12 05:02:45 UTC 2018 2018-06-12 20:58:07 +02:00
xap Wed Jun 6 22:19:01 UTC 2018 2018-06-07 08:58:09 +02:00
xfce Mon May 28 19:12:29 UTC 2018 2018-05-31 23:39: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