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 4ccd8ebc9a Wed Sep 12 21:19:38 UTC 2018
a/elilo-3.16-x86_64-8.txz:  Rebuilt.
  eliloconfig: this was occasionally failing and the issue was traced to the
  script's use of tr (not sure why still). Replaced the construct with sed
  and the issue seems to have gone away.
a/openssl-solibs-1.1.1-x86_64-1.txz:  Upgraded.
d/binutils-2.31.1-x86_64-3.txz:  Rebuilt.
  Do not install the Windows-specific tools. Not only are these useless on
  Linux, but the presence of windres fools freetype into thinking that it is
  on a Windows system, leading to a build failure.
d/git-2.19.0-x86_64-1.txz:  Upgraded.
l/freetype-2.9.1-x86_64-1.txz:  Upgraded.
l/harfbuzz-1.9.0-x86_64-1.txz:  Upgraded.
l/media-player-info-24-noarch-1.txz:  Upgraded.
l/pcre2-10.32-x86_64-1.txz:  Upgraded.
l/sg3_utils-1.43-x86_64-1.txz:  Upgraded.
n/openssl-1.1.1-x86_64-1.txz:  Upgraded.
x/fontconfig-2.13.1-x86_64-1.txz:  Upgraded.
  We had problem reports with fontconfig-2.13.0 which led to it being reverted
  but we'll try it again. Please let me know if the issues (with Wine iirc)
  persist.
x/libinput-1.12.0-x86_64-1.txz:  Upgraded.
2018-09-13 09:00:32 +02:00
..
a Wed Sep 12 21:19:38 UTC 2018 2018-09-13 09:00:32 +02:00
ap Mon Sep 10 21:00:00 UTC 2018 2018-09-11 03:00:39 +02:00
d Wed Sep 12 21:19:38 UTC 2018 2018-09-13 09:00:32 +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 Mon Sep 10 21:00:00 UTC 2018 2018-09-11 03:00:39 +02:00
k Mon Sep 10 21:00:00 UTC 2018 2018-09-11 03:00:39 +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 Wed Sep 12 21:19:38 UTC 2018 2018-09-13 09:00:32 +02:00
n Wed Sep 12 21:19:38 UTC 2018 2018-09-13 09:00:32 +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 Wed Sep 12 21:19:38 UTC 2018 2018-09-13 09:00:32 +02:00
xap Thu Sep 6 06:15:46 UTC 2018 2018-09-06 18:00:33 +02:00
xfce Mon Sep 10 21:00:00 UTC 2018 2018-09-11 03:00:39 +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