Release LXQt 2.0.0

https://lxqt-project.org/release/202...se-lxqt-2-0-0/

LXQt 2.0.0 updates to the same toolkit as KDE Plasma 6.
Meaning, no pain in the arse, I recommend to remove KDE.
Hopefully, Pat will upgrade to KDE6 shortly....makes everything easier.

Remove KDE groups.
Build QT6/KDE6 dependencies
Build LXQt core
Build some extras, LXQt-Apps, Openbox, Kvantum-QT6 etc.
Anyway, QTermwidget and QTerminal with QT6 is git based.

https://codeberg.org/snuk/lxqt-snuk-...ps/qtermwidget
https://codeberg.org/snuk/lxqt-snuk-...apps/qterminal

I am considering to create LXQt2 for 15.0 as well, but I am not sure yet.

Attached Thumbnails

 

If you add KDE back after the build and install , does it muck things up?

Yep, LXQt2 is QT6/KDE6 based.

@lancsuk

I saw that you recommend the complete uninstallation of Plasma5.

I think this is understandable with the mega-builds that LuckyCyborg makes either for KDE4 or Plasma6, but is this really the case with LxQt2?

I don't know about others, but for me it seems ridiculous to have to choose between the stock Plasma5 and LxQt2.

To be honest, I always looked at LxQt as a light version of Qt Destkop, not as a competitor of Plasma5. Something like XFCE4 is for GNOME4, which both tag along.

The LxQt 1.x is designed to tag along with Plasma5, BUT like @lancsuk already said, the LxQt2 is designed to tag along with Plasma6.

Honestly, I like the OP approach on building LxQt2 , as it does not really conflict with the Plasma6.

But if OP really want, he can make a build capable to tag along with the stock Plasma5, by renaming these several KDE Frameworks 6.x packages which are used.

Something like Mr. Hameleers did for his KTown of Plasma6 (and which I borrowed too) but in reverse - the KTown renames the KDE Frameworks 5.x packages which are all shipped by it.

1 members found this post helpful.

Here, I have plasma6 and lxqt2, installed, the two, with my own packages, all work without problems, and all compiled with qt6.6.7.

Thanks for confirming my point that per se, the LxQt2 is designed to tag along with Plasma6.

BUT, yes I agree that the requirement to remove entirely the Plasma5 seems harsh for someone non interested to jump on Plasma6 too.

i confirme, lxqt2 work perfectly with all Eric ktown based package, on the other hand here everything is updated ( dependencies, plasma-extra, qt6, etc.......).

I specify that I do not use openbox, I use kwin.

Yes, true, but I'd like to think about it.

Good News, I was able to install LXQT2 and KDE5 side by side. But, as expected some issues.

1. LXQT panel including modules failed to start.

Solution:
2. Instead QTerminal, the default terminal emulator was xterm.

Solution:
3. Default wallpaper didn't appear.

Solution:

3 members found this post helpful.

The reason to use 'jq' in deps ?

Yep, is relvant for c-shell users.

OK, thanks.

Well, with the packages you have in your repo, honestly I do not think that you are able to install LxQt2 along with Plasma5, because it replaces a series of stock packages to Plasma6, from both KDE Frameworks and KDE Plasma. So, certainly you have broken the Plasma5 while installing your packages.

https://codeberg.org/snuk/lxqt-snuk-current.git

If you want to install your dependencies (part of Plasma6) without replacing the stock packages, you will need to rename the packages, something like for solid to generate a package named: solid-6-6.1.0-x86_64-1_snuk.txz

So, according with my suggestion, the package name will be solid-6, which is not equal with the name of the stock solid package from KDE Frameworks 5.x.

Something like this do also Mr. Hameleers for his KTown for Plasma6, with which I thinker in the last time. Only that he did vice-versa, naming the legacy KDE Frameworks 5.x packages like solid-5