Just packaged LXQt-current. If you would like to take it for a spin, its in wip πŸ™‚

Make sure you install all the available dependencies to save build time πŸ˜‰
These are...

qt5-qtbase qt5-qtsvg qt5-qttools qt5-qtx11extras kwindowsystem libXScrnSaver polkit-qt5 openssh libdbusmenu-qt5 openbox libX11 sudo libXfixes upower solid kidletime kwayland libXcursor libXcomposite libdbusmenu-qt breeze-icons kguiaddons libstatgrab xdg-user-dirs lxmenu-data

After that you can clone wip and build the package,

cd /usr/pkgsrc/
git clone git://wip.pkgsrc.org/pkgsrc-wip.git wip
cd wip/lxqt
make
...
doas make install
doas make clean

Here's a screenshot of it. Sorry, no heavy customization πŸ™‚

    pin congratulations! πŸ™‚

    β€œOnly the paranoid survive.”

    ― Harold Finch
    NetBSD VPS , NetBSD , OS108

    • pin likes this.

    LXQt is ready πŸ™‚
    Its functional and can be used as a daily desktop. Although, I'm a spectrwm user and I'm happy to have a "clean system" again.

    • Jay likes this.
    3 months later

    LXQt-0.15.0 πŸ˜„

    Now, ...(running) back to spectrwm

    EDIT: 😌 nothing like home...

    • Jay likes this.

    never tried spectrwm, what do you like about it? is it like dwm?

    • pin replied to this.

      doug213 yes, without the need to re-compile πŸ™‚
      Just make your changes in .spectrwm.conf and re-load.

      18 days later

      0.14.1 is available from the repositories.
      Now, 0.15.0 in wip has been updated with yesterday's point releases for some of the components. Waiting for a final point release of lxqt-panel and some testing before importing. This is my personal build without sudo and pulseaudio πŸ™‚

      Do ask if you need anything.

        pin This is a very nice effort. Have you thought of porting the latest KWin? It is an amazing WM that uses few resources and does not require Plasma. KWin has tiling support, software compositing, window rules, and a possibility to set key bindings for almost every function.

        • pin replied to this.

          pin That is a shame. I suppose the code for KWin's ancestor (whatever it's been renamed to in the Trinity Desktop Environment) might be work a look. KWin in KDE 3.x was very nice as well, although I don't recall it having tiling support.

          • neb replied to this.
            8 days later

            😴 LXQt-0.15.0 imported.
            Thanks to David Gutteridge for working with me on this, you've been awesome.
            Thanks to Maya Rashish and Nikita Gillmann for reviewing.
            ...and a reference to Leonardo Taccari and Jonathan Perkin for their hints and critics.

            • Jay likes this.
            5 months later

            Does LxQt have a battery monitor?

            That "System Configuration" directory looks wrong. :/

            • pin replied to this.

              nia that's exactly what's still missing before importing, I have lxqt-powermanagement left to package.

              Hmm... wrong?!
              I'll look into it but, I haven't changed it from version 0.15.0.

              • Jay likes this.

              Examples is for... well, examples, not active configuration files.

              • pin replied to this.
              • Jay likes this.

                nia The whole path thing is a bit twisted on LXQt anyway but, as said, I'll look into it πŸ™‚

                kamil yes, and I thought it was a pity that is was getting outdated in wip, so I've decided to bring it back to life, even if don't use it myself.

                The new versions of LXQt are rather different from the old ones but, your work has allowed for a lot of it to be reused.

                The differences from 0.9.0 to todays 0.16.0 might be trivial to you or to anyone that knows C++ and/or other programming languages but, I'm not a programmer. Actually, my very first Linux Mint install was less than 4 years ago and I see myself as a simple user.

                When I started using NetBSD (because I was getting tired of Linux) there were a lot of things that I was missing. I still remember you helped me out in wip with qt5ct, molsketch and ufetch.
                Getting those packaged was the start of it all and thanks for making "life hard" on me back then πŸ˜ƒ and making me understand some of the basic concepts of packaging instead of "handing out" the solution.

                This made me stay on NetBSD, I could have just leave and go back to Linux, all the packages I wanted were just a simple
                sudo <some_package_manager> install <pkg_name> away.
                But, why would I do that? I'd just understood that, with some reading and persistence, I could get most of it packaged for the system I enjoy using.

                LXQt was a good practice, the foundations were there while the changes implemented by upstream during those years had made it challenging enough to be a good practice/learning playground.

                So, I've decided to give back to the project.
                Bringing desktop content is the sort of thing that brings in new users. Personally, there isn't much I'm missing anymore but, keeping users by helping them getting what they want/need is something I like doing, even if sometimes is a bit over my knowledge.

                Upstream LXQt has already started releasing some point releases, so there is no rush in getting 0.16.0 packaged.

                  pin This is great team work and something that makes an Open Source project more valuable for both contributors and users.

                  • Jay likes this.