slackware-current/source
Patrick J Volkerding 4e75b0d129 Tue Jan 12 22:20:40 UTC 2021
a/kernel-generic-5.10.7-x86_64-1.txz:  Upgraded.
a/kernel-huge-5.10.7-x86_64-1.txz:  Upgraded.
a/kernel-modules-5.10.7-x86_64-1.txz:  Upgraded.
a/libblockdev-2.25-x86_64-1.txz:  Upgraded.
ap/sudo-1.9.5p1-x86_64-1.txz:  Upgraded.
  Fixed a regression introduced in sudo 1.9.5 where the editor run by sudoedit
  was set-user-ID root unless SELinux RBAC was in use. The editor is now run
  with the user's real and effective user-IDs.
d/autoconf-2.69-noarch-2.txz:  Rebuilt.
  We're seeing failures using autoconf-2.70 with some packages that use
  autoreconf. It looks like most distributions have not moved on to
  autoconf-2.70, and probably we shouldn't either until the next release cycle.
  Thanks to nobodino.
d/kernel-headers-5.10.7-x86-1.txz:  Upgraded.
e/emacs-27.1-x86_64-2.txz:  Rebuilt.
  Increase SYSTEM_PURESIZE_EXTRA to 100000 to avoid overflows. Nobody should be
  too concerned about adding 97K to emacs' memory footprint given the amount of
  memory available on modern machines. Thanks to Jefferson for the bug report.
k/kernel-source-5.10.7-noarch-1.txz:  Upgraded.
l/libclc-11.0.1-x86_64-1.txz:  Upgraded.
  Thanks to USUARIONUEVO.
l/python-pygments-2.7.4-x86_64-1.txz:  Upgraded.
n/gnupg2-2.2.27-x86_64-1.txz:  Upgraded.
n/socat-1.7.4.1-x86_64-1.txz:  Upgraded.
x/libdrm-2.4.104-x86_64-1.txz:  Upgraded.
x/libevdev-1.10.1-x86_64-1.txz:  Upgraded.
x/vulkan-sdk-1.2.141.0-x86_64-2.txz:  Rebuilt.
  Install additional Vulkan-ValidationLayers-sdk header files.
  Thanks to walecha.
xap/mozilla-thunderbird-78.6.1-x86_64-1.txz:  Upgraded.
  This release contains security fixes and improvements.
  For more information, see:
    https://www.mozilla.org/en-US/thunderbird/78.6.1/releasenotes/
    https://www.mozilla.org/en-US/security/advisories/mfsa2021-02/
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16044
  (* Security fix *)
isolinux/initrd.img:  Rebuilt.
kernels/*:  Upgraded.
usb-and-pxe-installers/usbboot.img:  Rebuilt.
2021-01-13 08:59:49 +01:00
..
a Sun Jan 10 19:35:56 UTC 2021 2021-01-11 08:59:48 +01:00
ap Mon Jan 11 19:51:04 UTC 2021 2021-01-12 08:59:50 +01:00
d Tue Jan 12 22:20:40 UTC 2021 2021-01-13 08:59:49 +01:00
e Tue Jan 12 22:20:40 UTC 2021 2021-01-13 08:59:49 +01:00
f Mon May 28 19:12:29 UTC 2018 2018-05-31 23:39:35 +02:00
installer Sat Jan 9 20:53:30 UTC 2021 2021-01-10 08:59:50 +01:00
k Tue Jan 12 22:20:40 UTC 2021 2021-01-13 08:59:49 +01:00
kde Sat Jan 9 20:53:30 UTC 2021 2021-01-10 08:59:50 +01:00
l Tue Jan 12 22:20:40 UTC 2021 2021-01-13 08:59:49 +01:00
n Tue Jan 12 22:20:40 UTC 2021 2021-01-13 08:59:49 +01:00
t Sat Oct 31 01:29:37 UTC 2020 2020-10-31 08:59:53 +01:00
tcl Tue Jan 5 00:27:10 UTC 2021 2021-01-05 08:59:48 +01:00
x Tue Jan 12 22:20:40 UTC 2021 2021-01-13 08:59:49 +01:00
xap Tue Dec 29 20:34:54 UTC 2020 2020-12-30 08:59:52 +01:00
xfce Fri Jan 8 19:43:46 UTC 2021 2021-01-09 08:59:49 +01:00
y Wed Dec 30 21:56:42 UTC 2020 2020-12-31 08:59:47 +01:00
buildlist-from-changelog.sh Sat Jan 9 20:53:30 UTC 2021 2021-01-10 08:59:50 +01:00
make_world.sh Fri Jan 8 19:43:46 UTC 2021 2021-01-09 08:59:49 +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