1
0
Fork 0
mirror of git://slackware.nl/current.git synced 2025-01-14 08:01:11 +01:00
slackware-current/source
Patrick J Volkerding 77f4f1f5e6 Sat Sep 15 21:19:23 UTC 2018
a/kernel-firmware-20180913_44d4fca-noarch-1.txz:  Upgraded.
a/kernel-generic-4.14.70-x86_64-1.txz:  Upgraded.
a/kernel-huge-4.14.70-x86_64-1.txz:  Upgraded.
a/kernel-modules-4.14.70-x86_64-1.txz:  Upgraded.
ap/hplip-3.18.7-x86_64-4.txz:  Rebuilt.
  Applied fixed patch - this has a better chance of working now. I've checked
  and hpcups no longer links to libImageProcessor. Which, by the way, the
  previous build dumped onto my main system (not even in "make install"),
  but not into the package itself. I no longer own an HP printer and will
  never buy another one, so if there are any remaining problems please report.
  Thanks to Matteo Bernardini.
d/kernel-headers-4.14.70-x86-1.txz:  Upgraded.
k/kernel-source-4.14.70-noarch-1.txz:  Upgraded.
  Config changes since 4.14.69:
   CLEANCACHE n -> y
   CMA n -> y
   MEMORY_FAILURE n -> y
   NUMA n -> y
   X86_CHECK_BIOS_CORRUPTION n -> y
   Z3FOLD m -> y
   ZBUD m -> y
   ZSMALLOC m -> y
  +ACPI_APEI_MEMORY_FAILURE y
  +ACPI_NUMA y
  +AMD_NUMA y
  +CMA_AREAS 7
  +CMA_DEBUG n
  +CMA_DEBUGFS n
  +DMA_CMA n
  +HWPOISON_INJECT m
  +NEED_MULTIPLE_NODES y
  +NODES_SHIFT 6
  +NODES_SPAN_OTHER_NODES y
  +NUMA_BALANCING n
  +NUMA_EMU n
  +RAS_CEC n
  +USE_PERCPU_NUMA_NODE_ID y
  +X86_64_ACPI_NUMA y
  +X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK n
n/NetworkManager-1.14.0-x86_64-1.txz:  Upgraded.
  Added new options:  --enable-json-validation --enable-ovs
xap/network-manager-applet-1.8.18-x86_64-1.txz:  Upgraded.
isolinux/initrd.img:  Rebuilt.
kernels/*:  Upgraded.
pasture/php-5.6.38-x86_64-1.txz:  Upgraded.
  One security bug has been fixed in this release:
  Apache2: XSS due to the header Transfer-Encoding: chunked
  For more information, see:
    https://php.net/ChangeLog-5.php#5.6.38
  (* Security fix *)
usb-and-pxe-installers/usbboot.img:  Rebuilt.
2018-09-16 09:00:33 +02:00
..
a Thu Sep 13 21:41:51 UTC 2018 2018-09-14 09:00:31 +02:00
ap Sat Sep 15 21:19:23 UTC 2018 2018-09-16 09:00:33 +02:00
d Fri Sep 14 23:06:26 UTC 2018 2018-09-15 09:00:31 +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 Thu Sep 13 21:41:51 UTC 2018 2018-09-14 09:00:31 +02:00
k Sat Sep 15 21:19:23 UTC 2018 2018-09-16 09:00:33 +02:00
kde Tue Aug 21 18:39:27 UTC 2018 2018-08-22 09:00:30 +02:00
kdei Mon May 28 19:12:29 UTC 2018 2018-05-31 23:39:35 +02:00
l Fri Sep 14 23:06:26 UTC 2018 2018-09-15 09:00:31 +02:00
n Sat Sep 15 21:19:23 UTC 2018 2018-09-16 09:00:33 +02:00
t Wed Aug 22 23:44:25 UTC 2018 2018-08-23 09:00:32 +02:00
tcl Mon May 28 19:12:29 UTC 2018 2018-05-31 23:39:35 +02:00
x Fri Sep 14 23:06:26 UTC 2018 2018-09-15 09:00:31 +02:00
xap Thu Sep 6 06:15:46 UTC 2018 2018-09-06 18:00:33 +02:00
xfce Thu Sep 13 21:41:51 UTC 2018 2018-09-14 09:00:31 +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