sysutils/lxqt-powermanagement2.4.0_2

*/*: Bump PORTREVISION for known Qt private API abusers

Qt 6.11.2 edition.

These ports are known to directly use or link to a library that uses the
Qt private API and must be rebuilt with every Qt update.

Qt *public* API/ABI compatability is excellent, so most consumers don't
need to necessarily be rebuilt between patch or even minor releases, but
use of the private API breaks this compatibility between even patch
releases and its use is highly discouraged.

This list [1] is based on histortical data. We don't have time to
revisit every port on the list with each Qt update, so if your port has
dropped Qt private headers and was bumped in error, please remove it
yourself if you have write access to the Wiki or alert someone on kde@.

[1] https://wiki.freebsd.org/KDE/Qt

MFH:		2026Q3

*/*: Bump PORTREVISION for known Qt private API abusers

Qt 6.11.1 edition.

These ports are known to directly use or link to a library that uses the
Qt private API and must be rebuilt with every Qt update.

Qt *public* API/ABI compatability is excellent, so most consumers don't
need to necessarily be rebuilt between patch or even minor releases, but
use of the private API breaks this compatibility between even patch
releases and its use is highly discouraged.

This list [1] is based on histortical data. We don't have time to
revisit every port on the list with each Qt update, so if your port has
dropped Qt private headers and was bumped in error, please remove it
yourself if you have write access to the Wiki or alert someone on kde@.

[1] https://wiki.freebsd.org/KDE/Qt

x11-wm/lxqt: Update to 2.4.0

ChangeLog at:   https://lxqt-project.org/release/2026/04/20/release-lxqt-2-4-0/
With hat:       lxqt

*/*: Bump PORTREVISION for known Qt private API abusers

Qt 6.10.2 edition.

These ports are known to directly use or link to a library that uses the
Qt private API and must be rebuilt with every Qt update.

Qt *public* API/ABI compatability is excellent, so most consumers don't
need to necessarily be rebuilt between patch or even minor releases, but
use of the private API breaks this compatibility between even patch
releases and its use is highly discouraged.

This list [1] is based on histortical data. We don't have time to
revisit every port on the list with each Qt update, so if your port has
dropped Qt private headers and was bumped in error, please remove it
yourself if you have write access to the Wiki or alert someone on kde@.

[1] https://wiki.freebsd.org/KDE/Qt

*/*: Bump PORTREVISION for known Qt private API abusers

Qt 6.10.1 edition.

These ports are known to directly use or link to a library that uses the
Qt private API and must be rebuilt with every Qt update.

Qt *public* API/ABI compatability is excellent, so most consumers don't
need to necessarily be rebuilt between patch or even minor releases, but
use of the private API breaks this compatibility between even patch
releases and its use is highly discouraged.

This list [1] is based on histortical data. We don't have time to
revisit every port on the list with each Qt update, so if your port has
dropped Qt private headers and was bumped in error, please remove it
yourself if you have write access to the Wiki or alert someone on kde@.

[1] https://wiki.freebsd.org/KDE/Qt

x11-wm/lxqt: Update to 2.3.0

- Update x11/screengrab to 3.1.0
- Update editors/featherpad to 1.6.2
- Add xdg-desktop-portal like RUN_DEPENDS to xdg-desktop-portal-lxqt [1]

ChangeLog at:   https://lxqt-project.org/release/2025/11/05/release-lxqt-2-3-0/
With hat:       lxqt
PR:		290488
Reported by:	Siva Mahadevan <me at svmhdvn.name> [1]

sysutils/lxqt-powermanagement: Update to 2.2.1

With hat:       lxqt

*/*: Bump PORTREVISION for known Qt private API abusers

Qt 6.9.3 edition.

These ports are known to directly use or link to a library that uses the
Qt private API and must be rebuilt with every Qt update.

Qt *public* API/ABI compatability is excellent, so most consumers don't
need to necessarily be rebuilt between patch or even minor releases, but
use of the private API breaks this compatibility between even patch
releases and its use is highly discouraged.

This list [1] is based on histortical data. We don't have time to
revisit every port on the list with each Qt update, so if your port has
dropped Qt private headers and was bumped in error, please remove it
yourself if you have write access to the Wiki or alert someone on kde@.

[1] https://wiki.freebsd.org/KDE/Qt

MFH:		2025Q4

*/*: Bump PORTREVISION for known Qt private API abusers

Qt 6.9.2 edition.

These ports are known to directly use or link to a library that uses the
Qt private API and must be rebuilt with every Qt update.

Qt *public* API/ABI compatability is excellent, so most consumers don't
need to necessarily be rebuilt between patch or even minor releases, but
use of the private API breaks this compatibility between even patch
releases and its use is highly discouraged.

This list [1] is based on histortical data. We don't have time to
revisit every port on the list with each Qt update, so if your port has
dropped Qt private headers and was bumped in error, please remove it
yourself if you have write access to the Wiki or alert someone on kde@.

[1] https://wiki.freebsd.org/KDE/Qt

MFH:		2025Q3

sysutils/lxqt-powermanagement: Fix build

PR:		287744
Reported by:	Dean E. Weimer <dweimer _at_ dweimer.net>

devel/lxqt2-build-tools: Update to 2.2.1

- Bump PORTREVISION of some lxqt ports
- Fix build with plasma6 6.4.0

With hat:       lxqt
PR:		287604

*/*: Bump PORTREVISION for known Qt private API abusers

Qt 6.9.1 edition.

These ports are known to directly use or link to a library that uses the
Qt private API and must be rebuilt with every Qt update.

Qt *public* API/ABI compatability is excellent, so most consumers don't
need to necessarily be rebuilt between patch or even minor releases, but
use of the private API breaks this compatibility between even patch
releases and its use is highly discouraged.

This list of bumps is based on histortical data. We don't have time to
revisit every port on the list with each Qt update, so if your port has
dropped Qt private headers and was bumped in error, please let kde@ know
so we can correct this for future updates.

x11-wm/lxqt: Update to 2.2.0

ChangeLog at:   https://lxqt-project.org/release/2025/04/17/release-lxqt-2-2-0/

With hat:       lxqt

*/*: Bump PORTREVISION for known Qt private API abusers

Qt 6.8.3 edition.

These ports are known to directly use or link to a library that uses the
Qt private API and must be rebuilt with every Qt update.

Qt *public* API/ABI compatability is excellent, so most consumers don't
need to necessarily be rebuilt between patch or even minor releases, but
use of the private API breaks this compatibility even between patch
releases and its use is highly discouraged.

This list of bumps is based on histortical data. We don't have time to
revisit every port on the list with each Qt update, so if your port has
dropped Qt private headers and was bumped in error, please let kde@ know
so we can correct this for future updates.

Grep new entires for "_p.h". If they look Qt-ish, please reject. It's a
burden on the users at large and your local Qt maintainers to allow this
irresponsible behavior from downstream projects to continue.

*/*: Bump PORTREVISION for known Qt private API abusers

Qt 6.8.2 edition.

These ports directly use or link to a library that uses the Qt
private API and must be rebuilt with every Qt update.

Qt public API/ABI compatability is excellent, so most consumers don't
need to necessarily be rebuilt between patch or even minor releases, but
using the private API is highly discouraged since this is unstable even
between patch releases and is really only meant for internal use.

Adding devel/libqt6xdg and its consumers to the list this time around
based on [1].

PR:		283950 [1]

x11-wm/lxqt: Update to 2.1.0

This release add initial support for wayland. More information at:

https://github.com/lxqt/lxqt/wiki/ConfigWaylandSettings

Release highlights at:

https://lxqt-project.org/release/2024/11/05/release-lxqt-2-1-0/

With hat:       lxqt

x11-wm/lxqt: Update to 2.0.0

- Update mostly lxqt ports to 2.0.x
- Update some lxqt dependencies to latest version
- Update Mk/Uses/lxqt.mk file for support some legacy and new lxqt ports
- Add devel/libdbusmenu-lxqt
- Add x11/libfm-qt6
- Add devel/libqt6xdg
- Add sysutils/libsysstat-qt6
- Add devel/lxqt2-build-tools
- Add sysutils/lxqt-qt6plugin
- Add deskutils/xdg-desktop-portal-lxqt
- Add x11-toolkits/qtermwidget-qt5 for no break x11/coreterminal
- Pass maintainership to new lxqt@ group
- Few other modifications

PR:		278905
Approved by:	jsm

LXQt: update to 1.4.0

Changelog:
 https://lxqt-project.org/release/2023/11/05/release-lxqt-1-4-0/

PR:	277376

x11-wm/lxqt: Update to 1.3.0

PR:	271509

sysutils/lxqt-powermanagement: unbreak after 020693c166d1

CMake Error at /usr/local/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
  Could NOT find Perl (missing: PERL_EXECUTABLE)

PR:		266007
Reported by:	antoine (via exp-run)

sysutils/lxqt-powermanagement: Update to 1.2.0

Mk/Uses: always use colon for build/run suffix

Most USES use a colon for build/run(/test) suffixes. Change kde.mk,
qt.mk and pyqt.mk to do the same, and update all ports using that.

Document in CHANGES.

PR:			266034
Exp-run by:		antoine
Approved by:		tcberner (mentor)
Differential Revision:	https://reviews.freebsd.org/D36349

Remove WWW entries moved into port Makefiles

Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.

This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.

Approved by:		portmgr (tcberner)

Add WWW entries to port Makefiles

It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.

Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.

There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.

This commit implements such a proposal and moves one of the WWW: entries
of each pkg-descr file into the respective port's Makefile. A heuristic
attempts to identify the most relevant URL in case there is more than
one WWW: entry in some pkg-descr file. URLs that are not moved into the
Makefile are prefixed with "See also:" instead of "WWW:" in the pkg-descr
files in order to preserve them.

There are 1256 ports that had no WWW: entries in pkg-descr files. These
ports will not be touched in this commit.

The portlint port has been adjusted to expect a WWW entry in each port
Makefile, and to flag any remaining "WWW:" lines in pkg-descr files as
deprecated.

Approved by:		portmgr (tcberner)

sysutils/lxqt-powermanagement: Update to 1.1.0

sysutils/lxqt-powermanagement: Update to 1.0.0

*: Drop unused $FreeBSD$

New port: sysutils/lxqt-powermanagement

lxqt-powermanagement can monitor power management events and
optionally triggers actions like e.g. shut down a system when
laptop batteries are low on power.