mirror of
git://slackware.nl/current.git
synced 2025-01-31 19:57:23 +01:00
d2f4c4e59b
a/kernel-firmware-20210315_3568f96-noarch-1.txz: Upgraded. ap/sudo-1.9.6-x86_64-1.txz: Upgraded. d/cmake-3.19.7-x86_64-1.txz: Upgraded. d/python-setuptools-54.1.2-x86_64-1.txz: Upgraded. d/rust-1.50.0-x86_64-1.txz: Upgraded. l/libcap-2.49-x86_64-1.txz: Upgraded. l/python-urllib3-1.26.4-x86_64-1.txz: Upgraded. l/qt5-5.15.2-x86_64-6.txz: Rebuilt. Rebuilt with -proprietary-codecs and -webengine-proprietary-codecs. When combined with -webengine-ffmpeg (use system ffmpeg), this doesn't actually build any proprietary codecs, but allows them to be used if they happen to be built into the system ffmpeg. Thanks to alienBOB. xap/mozilla-firefox-86.0.1-x86_64-1.txz: Upgraded. When we first moved Slackware to the Firefox ESR channel, the motivation was to keep Firefox secure while delaying a requirement for Rust at build time. Of course, eventually that ESR version reached EOL and we had to introduce Rust into Slackware 14.2 in order to continue providing updates. Eventually that also ran into roadblocks as Firefox required first newer C/C++ compilers, and then finally a newer libstdc++. To continue, we'd have had to bump GCC to a much newer version, making other maintenance difficult or impossible. At this point, the latest Firefox has no additional dependencies beyond those of the ESR version, and it's unlikely that it will be any more difficult to keep it maintained. I think we all want the Slackware 15.0 release to be as good as possible, and most users will be better served if we resume following the latest desktop releases. Thanks to LuckyCyborg who can always be counted on to give me a friendly kick in the rear end. :-) Thanks also to ponce for the updated gkrust patch. |
||
|---|---|---|
| .. | ||
| 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