slackware-current/source
Patrick J Volkerding 05538a2b6d Wed Feb 6 00:29:25 UTC 2019
ap/linuxdoc-tools-0.9.73-x86_64-1.txz:  Upgraded.
  Upgraded to gtk-doc-1.29.
  Upgraded to asciidoc-8.6.10.
  Upgraded to perl-XML-SAX-1.00.
  Thanks to Stuart Winter.
d/meson-0.49.2-x86_64-1.txz:  Upgraded.
d/python-setuptools-40.8.0-x86_64-1.txz:  Upgraded.
d/slacktrack-2.19-x86_64-1.txz:  Upgraded.
  Thanks to Stuart Winter.
l/imagemagick-6.9.10_26-x86_64-1.txz:  Upgraded.
n/dovecot-2.3.4.1-x86_64-1.txz:  Upgraded.
  This update addresses security issues:
  CVE-2019-3814: If imap/pop3/managesieve/submission client has trusted
  certificate with missing username field (ssl_cert_username_field), under
  some configurations Dovecot mistakenly trusts the username provided via
  authentication instead of failing.
  ssl_cert_username_field setting was ignored with external SMTP AUTH,
  because none of the MTAs (Postfix, Exim) currently send the cert_username
  field. This may have allowed users with trusted certificate to specify any
  username in the authentication. This bug didn't affect Dovecot's
  Submission service.
  For more information, see:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3814
  (* Security fix *)
2019-02-06 08:59:42 +01:00
..
a Sat Jan 26 04:15:08 UTC 2019 2019-01-26 08:59:46 +01:00
ap Wed Feb 6 00:29:25 UTC 2019 2019-02-06 08:59:42 +01:00
d Wed Feb 6 00:29:25 UTC 2019 2019-02-06 08:59:42 +01:00
e Fri Sep 21 18:51:07 UTC 2018 2018-09-22 09:00:39 +02:00
f Mon May 28 19:12:29 UTC 2018 2018-05-31 23:39:35 +02:00
installer Sat Jan 26 20:44:46 UTC 2019 2019-01-27 08:59:47 +01:00
k Fri 01 Feb 2019 01:26:44 AM UTC 2019-02-01 08:59:45 +01:00
kde Mon Dec 31 21:33:54 UTC 2018 2019-01-01 08:59:45 +01:00
kdei Mon May 28 19:12:29 UTC 2018 2018-05-31 23:39:35 +02:00
l Mon Feb 4 21:50:36 UTC 2019 2019-02-05 08:59:45 +01:00
n Wed Feb 6 00:29:25 UTC 2019 2019-02-06 08:59:42 +01:00
t Wed Nov 28 07:25:32 UTC 2018 2018-11-28 17:59:44 +01:00
tcl Sat Nov 24 20:44:07 UTC 2018 2018-11-25 08:59:43 +01:00
x Wed Jan 30 04:27:03 UTC 2019 2019-01-30 17:59:47 +01:00
xap Wed Jan 30 04:27:03 UTC 2019 2019-01-30 17:59:47 +01:00
xfce Wed Jan 30 04:27:03 UTC 2019 2019-01-30 17:59:47 +01:00
y Fri Sep 21 18:51:07 UTC 2018 2018-09-22 09:00:39 +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 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