mirror of
git://slackware.nl/current.git
synced 2024-11-16 07:48:02 +01:00
c73f45c6d4
Clearly we're going to have to trend more carefully for things to settle down, so consider this RC2 and a much harder freeze. A test mass rebuild was done here and there are no more "fails to build from source" remaining (thanks to nobodino for some amazing and relentless testing). a/exfatprogs-1.1.3-x86_64-1.txz: Upgraded. ap/lxc-4.0.11-x86_64-3.txz: Rebuilt. Added some additional packages to the lxc-slackware template: bridge-utils, dbus, iptables, libnl3, libpcap. Thanks to linux91 for the hints. ap/qpdf-10.4.0-x86_64-1.txz: Upgraded. l/python-docutils-0.17.1-x86_64-3.txz: Rebuilt. Revert to this version for now since 0.18 isn't compatible with Sphinx. Thanks to HQuest. l/python-markdown-3.3.4-x86_64-3.txz: Rebuilt. Reverted this to fix the Samba build. The newer versions of Markdown require importlib_metadata and zipp, and adding these also fixes the build, but oddly the installed PKG-INFO shows version 0.0.0, which I suspect is more breakage going on with setuptools. I've tried rebuilding all other Python modules here to see if a more general breakage had crept in somehow, but those are the only two Python modules I've found that exhibit this issue, and I've found other similar reports (but no fixes). Markdown-3.3.4 seems to be the safe bet for now. n/bind-9.16.23-x86_64-1.txz: Upgraded. x/libdrm-2.4.107-x86_64-1.txz: Upgraded. Reverted to 2.4.107 as 2.4.108 does not seem to be completely compatible with xorg-server-1.20.13. Fixes xf86-video-vmware failing to build from source. Thanks to nobodino. |
||
|---|---|---|
| .. | ||
| 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