1
0
Fork 0
mirror of git://slackware.nl/current.git synced 2025-01-28 08:02:25 +01:00
slackware-current/source
Patrick J Volkerding eba2e5b781 Fri May 15 07:28:15 UTC 2020
Hey folks, just a heads-up that PAM is about to be merged into the main tree.
We can't have it blocking other upgrades any longer. The config files could be
improved (adding support for pam_krb5 and pam_ldap, for example), but they'll
do for now. Have a good weekend, and enjoy these updates! :-)
a/aaa_elflibs-15.0-x86_64-23.txz:  Rebuilt.
  Upgraded: libcap.so.2.34, libelf-0.179.so, liblzma.so.5.2.5,
  libglib-2.0.so.0.6400.2, libgmodule-2.0.so.0.6400.2,
  libgobject-2.0.so.0.6400.2, libgthread-2.0.so.0.6400.2,
  liblber-2.4.so.2.10.13, libldap-2.4.so.2.10.13, libpcre2-8.so.0.10.0.
  Added temporarily in preparation for upgrading icu4c: libicudata.so.65.1,
  libicui18n.so.65.1, libicuio.so.65.1, libicutest.so.65.1, libicutu.so.65.1,
  libicuuc.so.65.1.
a/etc-15.0-x86_64-11.txz:  Rebuilt.
  /etc/passwd: Added ldap (UID 330).
  /etc/group: Added ldap (GID 330).
a/kernel-generic-5.4.41-x86_64-1.txz:  Upgraded.
a/kernel-huge-5.4.41-x86_64-1.txz:  Upgraded.
a/kernel-modules-5.4.41-x86_64-1.txz:  Upgraded.
a/pkgtools-15.0-noarch-33.txz:  Rebuilt.
  setup.services: added support for rc.openldap and rc.openvpn.
ap/hplip-3.20.5-x86_64-1.txz:  Upgraded.
d/kernel-headers-5.4.41-x86-1.txz:  Upgraded.
d/python-setuptools-46.3.0-x86_64-1.txz:  Upgraded.
d/python3-3.8.3-x86_64-1.txz:  Upgraded.
k/kernel-source-5.4.41-noarch-1.txz:  Upgraded.
n/openldap-2.4.50-x86_64-1.txz:  Added.
  This is a complete OpenLDAP package with both client and server support.
  Thanks to Giuseppe Di Terlizzi for help with the server parts.
n/openldap-client-2.4.50-x86_64-1.txz:  Removed.
x/mesa-20.0.7-x86_64-1.txz:  Upgraded.
isolinux/initrd.img:  Rebuilt.
kernels/*:  Upgraded.
testing/packages/PAM/hplip-3.20.5-x86_64-1_pam.txz:  Upgraded.
usb-and-pxe-installers/usbboot.img:  Rebuilt.
2020-05-15 17:59:53 +02:00
..
a Fri May 15 07:28:15 UTC 2020 2020-05-15 17:59:53 +02:00
ap Tue May 12 23:49:47 UTC 2020 2020-05-13 08:59:54 +02:00
d Sun May 10 23:34:28 UTC 2020 2020-05-11 08:59:53 +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 Sat May 9 20:49:43 UTC 2020 2020-05-10 08:59:54 +02:00
k Fri May 15 07:28:15 UTC 2020 2020-05-15 17:59:53 +02:00
kde Sat May 9 20:49:43 UTC 2020 2020-05-10 08:59:54 +02:00
kdei Mon Sep 30 21:08:32 UTC 2019 2019-10-01 08:59:50 +02:00
l Wed May 13 20:01:12 UTC 2020 2020-05-14 08:59:52 +02:00
n Fri May 15 07:28:15 UTC 2020 2020-05-15 17:59:53 +02:00
t Mon Oct 7 04:41:29 UTC 2019 2019-10-07 17:59:47 +02:00
tcl Sat May 9 20:49:43 UTC 2020 2020-05-10 08:59:54 +02:00
x Fri May 1 18:05:38 UTC 2020 2020-05-02 08:59:53 +02:00
xap Tue May 12 23:49:47 UTC 2020 2020-05-13 08:59:54 +02: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