AUR (en) - liblxqt-git

Git Clone URL:	https://aur.archlinux.org/liblxqt-git.git (read-only, click to copy)
Package Base:	liblxqt-git
Description:	Common base library for LXQt components.
Upstream URL:	https://lxqt-project.org
Licenses:	LGPL-2.1-only
Conflicts:	liblxqt
Provides:	liblxqt
Submitter:	jleclanche
Maintainer:	yan12125 (pmattern)
Last Packager:	pmattern
Votes:	52
Popularity:	0.000000
First Submitted:	2013-10-24 00:54 (UTC)
Last Updated:	2024-04-24 09:24 (UTC)

Latest Comments

pmattern commented on 2024-05-07 19:21 (UTC)

Speaking of "comparing" I was actually thinking of easily comparing VCS and release package with an AUR helper like yaourt.
But actually that's not really the point anyway.

Looking through this package's commit history suggests the epoch was unneeded right from the beginning. It shouldn't have been introduced in the first place.
Also, it's inconsistent with all other LXQt-related VCS packages.
And it does not make any sense at all to stick with something completely faulty, just because its removal may cause some temporary glitches.
So sorry, but I for one am still completely against re-introducing it.

yan12125 commented on 2024-05-01 06:32 (UTC)

preventing reasonable version comparison between VCS and release package.

Thanks for the reply. As liblxqt-git and liblxqt are different packages from the perspective of pacman, I assume "comparison" means manual comparisons by human or by scripts? In those cases, epochs can be easily ignored.

pmattern commented on 2024-04-26 20:58 (UTC)

Yes, removing variable epoch may trick users into missing updates. But this only happens, if they do not really pay attention and e. g. blindly follow some AUR helper. This should be avoided anyway. And in particular, I wouldn't expect it to be a problem for the special breed that VCS package users are.
The variable itself on the other hand is right now not only useless but can have undesired effects like preventing reasonable version comparison between VCS and release package.
So when removing it, I was fully aware of possible pitfalls but believing that the pros outweigh the cons. And tbh. I still think so.

Maybe we can, as a comprise, add a temporarily pinned comment pointing users to the removal.

yan12125 commented on 2024-04-26 14:40 (UTC)

pmattern: many thanks for updates, but I'm not sure if it's a good idea to drop eopch. Users may always have a newer version than the one on AUR, so they may not get future updates.

isf63 commented on 2023-10-20 11:55 (UTC)

kwindowsystem is now kwindowsystem5 - which prevents the build

yan12125 commented on 2017-10-15 10:15 (UTC)

This package is broken as lxqt-build-tools is outdated: CMake Error at CMakeLists.txt:132 (find_package): Could not find a configuration file for package "lxqt-build-tools" that is compatible with requested version "0.4.0". The following configuration files were considered but not accepted: /usr/share/cmake/lxqt-build-tools/lxqt-build-tools-config.cmake, version: 0.3.2 Either updating lxqt-build-tools in [community] or using lxqt-build-tools-git instead solves the problem. I vote for the latter as liblxqt-git may depend on lxqt-build-tools 0.5.0 one day, before lxqt-build-tools is updated again.