mirror of
git://slackware.nl/current.git
synced 2025-01-14 08:01:11 +01:00
409d51497d
a/kernel-firmware-20200824_74bd44f-noarch-1.txz: Upgraded. ap/vim-8.2.1522-x86_64-1.txz: Upgraded. l/libuv-1.39.0-x86_64-1.txz: Upgraded. x/libX11-1.6.12-x86_64-1.txz: Upgraded. x/xorg-server-1.20.9-x86_64-1.txz: Upgraded. x/xorg-server-xephyr-1.20.9-x86_64-1.txz: Upgraded. x/xorg-server-xnest-1.20.9-x86_64-1.txz: Upgraded. x/xorg-server-xvfb-1.20.9-x86_64-1.txz: Upgraded. x/xorg-server-xwayland-1.20.9-x86_64-1.txz: Upgraded. xap/vim-gvim-8.2.1522-x86_64-1.txz: Upgraded. testing/packages/mozilla-thunderbird-78.2.0-x86_64-1.txz: Added. https://www.mozilla.org/en-US/thunderbird/78.2.0/releasenotes/ I'm putting this into /testing first so that any problems with OpenPGP can be reported before it goes into the main tree. Here's the current status from the release notes and Thunderbird:OpenPGP wiki page: Add-on support: As of version 78.0, Thunderbird only supports MailExtensions. Your favorite add-ons may not have been updated for compatibility. At this time, users of the Enigmail Add-on should not update to Thunderbird 78. OpenPGP in Thunderbird 78.2.0 has reached feature complete state, but it's still disabled by default, to allow more time for testing, correctness, and localization. See the wiki for how to enable and help with testing. If you use OpenPGP for non-critical purposes, then you are welcome to enable it manually and help with testing. To enable it in Thunderbird 78.0, use the config editor and change the value of preference mail.openpgp.enable to true, then restart Thunderbird. If you are running 78.x and have the previous Enigmail Add-on installed, then Enigmail will update to version 2.2.x, which is a minimal release that helps you to migrate the keys and settings to Thunderbird 78. If you haven't used Enigmail previously, you can enable OpenPGP for an email account in account settings. See the release notes for more complete information about testing and reporting bugs. |
||
|---|---|---|
| .. | ||
| a | ||
| ap | ||
| d | ||
| e | ||
| f | ||
| installer | ||
| k | ||
| kde | ||
| kdei | ||
| 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