diff options
Diffstat (limited to '')
| -rw-r--r-- | README.5_20.08 (renamed from README.5_20.06) | 164 |
1 files changed, 74 insertions, 90 deletions
diff --git a/README.5_20.06 b/README.5_20.08 index 47abb24..a680e61 100644 --- a/README.5_20.06 +++ b/README.5_20.08 @@ -1,22 +1,26 @@ KDE5 ==== -BIG FAT NOTICE: - This monthly release of Alien's ktown is a major prep test - for replacing ConsoleKit2 with elogind in Slackware-current. - Read the instructions carefully! In short: - - UPGRADE TO THE LATEST slackware-current first. - - Then, REMOVE the ConsoleKit2 package. - - Finally, install or upgrade the KDE5 package set. - -This is (unsurprisingly) KDE 5_20.06 for Slackware, consisting of -KDE Frameworks 5.71.0, Plasma 5.19.1 and Applications 20.04.2 +# ------------------------------------------------------------------------- # +# BIG FAT NOTICE: # +# Alien's ktown is changing your Slackware-current system and replaces # +# ConsoleKit2 with elogind. Read the instructions carefully! In short: # +# - UPGRADE TO THE LATEST slackware-current first. # +# - Then, REMOVE the ConsoleKit2 package (if it is still installed). # +# - Finally, install or upgrade the KDE5 package set. # +# - Ensure you put any *.new files into their correct locations # +# (a 'slackpkg new-config' will help). # +# - Reboot. # +# ------------------------------------------------------------------------- # + +This is KDE 5_20.08 for Slackware, consisting of: +KDE Frameworks 5.72.0, Plasma 5.19.4 and Applications 20.04.3; on top of Slackware's Qt 5.15.0. -Upgrading from the previous 5_20.05 should be done with care! If you do not -follow directions, your system will no longer allow you in! +Upgrading from the previous 5_20.06 should be done with care, but since you +should already have migrated to elogind, I do not expect anything will break. -KDE-5_20.06 is meant to be installed on top of Slackware -current. +KDE-5_20.08 is meant to be installed on top of Slackware -current. It will *replace* any version of KDE 4 you might have installed! The Plasma 5 Desktop has gotten rid of its Qt4 legacy. Since the release of Applications 17.12 there's nothing left which is based on kdelibs4. @@ -24,66 +28,41 @@ Slackware-current has begun its slow adoptation of the Plasma5 dependencies. Most importantly, QT5 and its dependencies are already part of Slackware. What is the NEWS in this batch of updates: -- Last month was the first release on top of a PAM-ified Slackware. I thought - I was done with public updates and continued experimenting in private, - but then a discussion on LinuxQuestions.org started because some people - seem to watch my git repository and noticed that I created a new 'elogind' - branch there. The discussion resolved a dead-end for me and I decided to - make a deal with Patrick. A new 'ktown' release targeting a fully - functional Plasma Wayland session. - And so, this month we take another major step. ConsoleKit2 which has been our - Session/Seat Manager for a long time, is going to be replaced with elogind. - The elogind code, similar to eudev which is already in Slackware, is a piece - of the systemd codebase (notably, systemd-logind) which was extracted and - modified so that it is no longer depending on systemd at all. - Slackware needs elogind if we are ever to provide a Wayland desktop next to - the venerable X.Org desktop environment. It seems like ConsoleKit2 is no - longer actively maintained and that means, other developers are no longer - maintaining compatibility with it (ConsoleKit2 and elogind offer similar - functionality but a program which needs that functionality must explicitly - carry the code to support both). - This time we are taking a joint approach. - Pat Volkerding has modified '/etc/rc.d/rc.M' inside the sysvinit-scripts - package, and '/etc/pam.d/login' inside the util-linux package in - slackware-current to be compatible with both ConsoleKit2 and elogind. - I have added elogind to 'ktown' and rebuilt the Slackware packages dbus and - polkit to pick up support for elogind (losing support for CK2 in the - process). +- In May we had the first release on Plasma5 on a PAM-ified Slackware, and + in June I went along and replaced ConsoleKit2 with elogind - a requirement + to make a KDE Plasma Wayland graphical session work. * * * Note that only one of the two (ConsoleKit2 or elogind) must be installed! * - * If you install ktown KDE-5_20.06 you need to remove ConsoleKit2! * + * If you install ktown KDE-5_20.08 you need to remove ConsoleKit2! * * * -- So, this leads to the following package updates in 'deps'. - * added the package autoconf-archive which was needed to recompile dbus. - * added elogind (make sure to 'removepkg ConsoleKit2' first!) - * added recompiled Slackware packages with elogind support: dbus and polkit. - * recompiled accountsservice to pick up elogind support - * recompiled polkit-qt5, libdbusmenu-qt5, qca-qt5 against the new Qt5, - which got an upgrade in Slackware since last month's 'ktown' release. - * recompiled grantlee-qt4 because I had forgotten to do so after the 2018 - mass rebuild in Slackware... no-one noticed. -- Frameworks 5.71.0 is an incremental stability release, see also: - https://kde.org/announcements/kde-frameworks-5.71.0 - The packages which pick up elogind support are: solid. -- Plasma 5.19.1 is the second increment of the 5.19 cycle, which means - that I skipped the .0 release. - See https://kde.org/announcements/plasma-5.19.1 and if you want to +- The 'deps' section got a bit smaller again this month: + * pcaudiolib, espeak-ng, hack-fonts-ttf, noto-fonts-ttf, and + noto-cjk-fonts-ttf were moved into the actual Slackware distro; + * flite has been removed since Pat decided we will go with just espeak-ng; + * a new package 'pipewire' was added as a dependency for krfb and + xdg-desktop-portal-kde. + * The elogind-aware dbus package was upgraded to match the Slackware version. + * Finally, qca-qt5 was upgraded and I recompiled mlt (to fix the broken + kdenlive) and speech-dispatcher. +- Frameworks 5.72.0 is an incremental stability release, see also: + https://kde.org/announcements/kde-frameworks-5.72.0 + A new 'kdav' source tarball got added but that is actually the same package + you'll find in KDEPIM. Next batch, the actual kdav package will be built + from Frameworks sources. +- Plasma 5.19.4 is an increment of the 5.19 cycle to add stability & fix bugs. + See https://kde.org/announcements/plasma-5.19.4 and if you want to read more about the goals for 5.19 you should check out: https://kde.org/announcements/plasma-5.19.0 - There is a new package in here: kwayland-server. - The packages which pick up elogind support are: plasma-workspace, - powerdevil, kscreenlocker. -- In plasma-extra I rebuilt sddm-qt5 to pick up elogind support and added - plasma-wayland-protocols as dependency for the new kwayland-server in Plasma. -- Applications 20.04.2 is an incremental bug fix release, see also - https://kde.org/announcements/releases/2020-06-apps-update/ -- For applications-extra, I tried (and failed) to update krita - and updated kmymoney. +- In plasma-extra I rebuilt sddm-qt5 to install man pages correctly, and + upgraded plasma-wayland-protocols and wacomtablet. +- Applications 20.04.3 is an incremental bug fix release, see also + https://kde.org/announcements/releases/2020-07-apps-update/ +- For applications-extra I updated digikam, krita, libktorrent and ktorrent, + and skanlite. Note that the size of the digikam source tarball 'blew up' + due to the addition of new neural network facial recognition data files, + but the actual package 'only' grew from 97 to 108 MB. Further points of interest: -- If you have a KDE4-based application that needs library support on this - Plasma 5 desktop, let me know which of the removed packages needs to return - in 'kde/kde4'! - There are a couple of *runtime* dependencies that I did not add to the ktown repository, but you may want to consider installing them yourself: * vlc - will give phonon another backend to select from. @@ -97,13 +76,12 @@ Further points of interest: applications to dock into the Plasma 5 system tray, more dependencies were needed. Apart from updates to regular Slackware packages the new ones are: accountsservice, autoconf-archive, cfitsio, cryptopp, cryfs, ddcutil, - dotconf, drumstick, dvdauthor, elogind , espeak-ng, flite, freecell-solver, - frei0r-plugins, grantlee-qt4, hack-font-ttf, id3lib, lensfun, - libappindicator, libburn, libdbusmenu-gtk, libdbusmenu-qt5, libdmtx, - libindicator, libsass, md4c, mlt, noto-font-ttf, noto-cjk-font-ttf, opencv, - pcaudiolib, perl-path-tiny, perl-template-toolkit, polkit-qt5-1, - python3-random2, quazip, qca-qt5, qrencode, qtav, rttr, sassc, sni-qt, - speech-dispatcher, and vid.stab + dotconf, drumstick, dvdauthor, elogind , freecell-solver, frei0r-plugins, + grantlee-qt4, lensfun, libappindicator, libburn, libdbusmenu-gtk, + libdbusmenu-qt5, libdmtx, libindicator, libsass, md4c, mlt, opencv, + perl-path-tiny, perl-template-toolkit, polkit-qt5-1, python3-random2, + quazip, qca-qt5, qrencode, qtav, rttr, sassc, sni-qt, speech-dispatcher, + and vid.stab . The phonon and poppler packages were extended so that they now support Qt5 as well as Qt4. The gpgme package picked up Qt5 support. Note that the SBo version of 'frei0r-plugins' package is called 'frei0r'. @@ -119,6 +97,12 @@ Also explained in more detail below, upgrading to this KDE 5 is non-trivial. You will have to remove old KDE 4 packages manually. NOTE: +If this time you removed ConsoleKit2 and installed elogind, be sure to +reboot your computer before attempting to login. Also be very sure that +you moved all the *.new files into place before you reboot (the command +'slackpkg new-config' can help you do that). + +NOTE: If you had installed KDE 4 as your default desktop previously, the removal of KDE 4 packages will break the symbolic link '/etc/X11/xinit/xinitrc'. An attempt to run 'startx' in a console will fail with a black screen. @@ -198,13 +182,19 @@ If you have Slackware 14.2 or -current's default KDE 4.14.3 installed: Alternatively, in case you are already using an older release of my KDE 5 packages, you need to look up that particular release in the list right below -(for instance: KDE 5_19.11) and then apply the actions shown for that KDE 5 +(for instance: KDE 5_20.02) and then apply the actions shown for that KDE 5 release *and* all more recent releases, i.e. work your way back up to this paragraph. Note that some of the old KDE package names were obsoleted along the way, they were split up, renamed or integrated and that is the reason for some of the 'removepkg' lines you'll see below. Here we go: +If you have my 'ktown' set of KDE 5_20.06 installed: +- Upgrade to KDE 5_20.08 + Remove the packages that no longer exist in KDE 5_20.08: + # removepkg flite + If you do need flite, consider building it from slackbuilds.org. + If you have my 'ktown' set of KDE 5_20.05 installed: - UPGRADE TO THE LATEST slackware-current first. - Then, REMOVE ConsoleKit2: @@ -238,14 +228,6 @@ If you have my 'ktown' set of KDE 5_20.01 installed: # removepkg polkit-kde-kcmodules-framework If you have my 'ktown' set of KDE 5_19.12 installed: -- No further actions are needed. - -If you have my 'ktown' set of KDE 5_19.11 installed: -- Upgrade to KDE 5_19.12 - Remove the packages that no longer exist in KDE 5_19.12: - # removepkg qt-gstreamer - -If you have my 'ktown' set of KDE 5_19.10 installed: - Really? A full re-install may be wiser. Proceed with installing/upgrading KDE 5 as outlined below. @@ -322,10 +304,12 @@ A graphical (ncurses) tool for processing these "*.new" files is slackpkg: # slackpkg new-config Then reboot your system. -IF this is the first time you run Plasma5, be aware that Baloo will -tax your CPU fairly heavily for a while as it indexes the content of -the files on your hard disk. After this initial indexing operation finishes, -(could take several hours) Baloo will get out of your way and stay there. +If this is the first time you run Plasma5, and you enable Baloo file indexing, +be aware that Baloo will tax your CPU fairly heavily for a while as it indexes +the content of the files on your hard disk. +After this initial indexing operation finishes (could take several hours), +Baloo will get out of your way and stay there. +This is why indexing is disabled by default. If all you want is to install the packages I created, then you can skip the remainder of the README which details how to (re)compile the packages from @@ -343,10 +327,10 @@ If you want the sources for KDE 5, run the following command to download them There are a lot of 'dependencies' for KDE 5 which you'll have to compile and install before attempting to compile KDE 5. Compiling and installing these -dependencies on Slackware-current is hopefully (have not tested the scripts -'updates.SlackBuild' and 'alldeps.SlackBuild' in a long time) as easy as this: +dependencies on Slackware-current is hopefully (have not tested the script +'alldeps.SlackBuild' in a long time) as easy as this: # cd sources/deps - # ./updates.SlackBuild + # ./alldeps.SlackBuild # cd - The finished packages will be stored in /tmp and will already have been @@ -362,4 +346,4 @@ Reboot your computer and login to a Plasma session. ============================================================================== - Eric Hameleers / alien at slackware dot com / 18-jun-2020 + Eric Hameleers / alien at slackware dot com / 01-aug-2020 |