Miroirs/slackware-current
1
0
Fork 0
mirror of git://slackware.nl/current.git synced 2025-01-27 07:59:56 +01:00
Code Issues Projects Releases Packages Wiki Activity
slackware-current/source
History
Patrick J Volkerding 8a7ca20f48 Sat Sep 28 19:23:35 UTC 2019 
a/f2fs-tools-1.13.0-x86_64-1.txz:  Upgraded.
  Shared library .so-version bump.
ap/rpm-4.15.0-x86_64-1.txz:  Upgraded.
  Shared library .so-version bump.
d/rust-1.38.0-x86_64-1.txz:  Upgraded.
  It seems that rust-1.38.0 builds fewer shared objects causing the package
  size to bloat to almost double. I held this back overnight to compile some
  modified builds to see if the old build behavior could be restored but
  didn't have any luck, so I'll put this out as-is for now. Any help debloating
  this package would be appreciated. Note that it also had to be bootstrapped
  from the official binaries using LOCAL_BOOTSTRAP=NO. That's not all that
  unusual for Rust, but perhaps that's another problem...
l/fribidi-1.0.7-x86_64-1.txz:  Upgraded.
l/fuse3-3.7.0-x86_64-1.txz:  Upgraded.
n/fetchmail-6.4.1-x86_64-1.txz:  Upgraded.
2019-09-29 08:59:48 +02:00
..
a Mon Sep 23 22:15:50 UTC 2019 2019-09-24 08:59:42 +02:00
ap Sat Sep 28 19:23:35 UTC 2019 2019-09-29 08:59:48 +02:00
d Sat Sep 28 19:23:35 UTC 2019 2019-09-29 08:59:48 +02:00
e Thu Aug 29 22:21:17 UTC 2019 2019-08-30 08:59:47 +02:00
f Mon May 28 19:12:29 UTC 2018 2018-05-31 23:39:35 +02:00
installer Wed Aug 21 19:21:45 UTC 2019 2019-08-22 08:59:48 +02:00
k Sat Sep 21 21:27:39 UTC 2019 2019-09-22 08:59:49 +02:00
kde Wed Aug 21 05:50:41 UTC 2019 2019-08-21 17:59:45 +02:00
kdei Mon May 28 19:12:29 UTC 2018 2018-05-31 23:39:35 +02:00
l Sat Sep 28 19:23:35 UTC 2019 2019-09-29 08:59:48 +02:00
n Sat Sep 28 19:23:35 UTC 2019 2019-09-29 08:59:48 +02:00
t Sun Jun 30 22:45:12 UTC 2019 2019-07-01 08:59:47 +02:00
tcl Fri Jul 12 18:52:15 UTC 2019 2019-07-13 08:59:47 +02:00
x Thu Sep 26 19:18:19 UTC 2019 2019-09-27 08:59:48 +02:00
xap Tue Sep 24 21:18:36 UTC 2019 2019-09-25 08:59:48 +02:00
xfce Sat Aug 17 20:39:30 UTC 2019 2019-08-18 08:59:47 +02:00
y Sun Feb 17 23:44:53 UTC 2019 2019-02-18 08:59:47 +01: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

README.TXT 

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