mirror of
git://slackware.nl/current.git
synced 2025-01-14 08:01:11 +01:00
abdca401c7
a/mkinitrd-1.4.11-x86_64-24.txz: Rebuilt. Change mkinitrd shebang to #!/bin/bash. Thanks to mumahendras3. Still, don't point /bin/sh at a shell other than bash. Only include dm-snapshot if LVM is included. Thanks to j12i. a/tcsh-6.22.04-x86_64-1.txz: Upgraded. ap/mariadb-10.6.0-x86_64-1.txz: Upgraded. Removed TokuDB stuff from rc.mysqld. Thanks to gsl. This update fixes the illegal instruction regession on 32-bit with processors that do not support SSE4.1 instructions. Thanks to Noel and Charlie Wilder for reporting the issue upstream and Matteo Bernardini for helping with the debugging. And of course, thanks to the MariaDB upstream developers. :-) |
||
---|---|---|
.. | ||
a | ||
ap | ||
d | ||
e | ||
f | ||
installer | ||
k | ||
kde | ||
l | ||
n | ||
t | ||
tcl | ||
x | ||
xap | ||
xfce | ||
y | ||
buildlist-from-changelog.sh | ||
make_world.sh | ||
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