[Midnightbsd-cvs] [MidnightBSD/mports] 74be63: x11/plasma6-plasma: add missing kwayland-integrati...

[Lucas Holt]

  Branch: refs/heads/master
  Home:   https://github.com/MidnightBSD/mports
  Commit: 74be63821c5c117a734c34b9410d2f029d4dc2c0
      https://github.com/MidnightBSD/mports/commit/74be63821c5c117a734c34b9410d2f029d4dc2c0
  Author: Lucas Holt <luke at foolishgames.com>
  Date:   2026-09-20 (Sun, 20 Sep 2026)

  Changed paths:
    M x11/plasma6-plasma/Makefile

  Log Message:
  -----------
  x11/plasma6-plasma: add missing kwayland-integration Qt5 dependency (#1500)

The `QT5` option (on by default) installs the Plasma 6 integration
plugins for Qt5 applications, but `QT5_RUN_DEPENDS` was missing
`plasma6-kwayland-integration-qt5`. `x11/plasma6-kwayland-integration`
is already in the tree and builds exactly that package, so the Wayland
integration plugins were never pulled in by the meta port. FreeBSD's
copy of this port lists all three; ours listed two.

`PORTREVISION` bumped.

### How this surfaced

The meta port packaged fine but would not install, failing on:

```
===>   plasma6-plasma-6.6.6 depends on package: plasma6-plasma-integration-qt5>0 - not found
CMake Error at /usr/local/lib/cmake/Qt5QuickControls2/Qt5QuickControls2Config.cmake:99 (find_package)
```

That turned out to be **build-box staleness, not a port bug**:
`Qt5QuickControls2Config.cmake` requires `Qt5Quick 5.15.19`, but the box
still had Qt5 at **5.15.18** while the tree is at **5.15.19**. 35
installed `qt5-*` packages were behind; 18 of them are in this port's
dependency graph.

### Testing

Rebuilt the 18 stale Qt5 ports in dependency order — all `EXIT=0`:

```
devel/qt5-qmake, devel/qt5-buildtools, devel/qt5-core, databases/qt5-sql,
devel/qt5-testlib, textproc/qt5-xml, net/qt5-network, devel/qt5-dbus,
devel/qt5-concurrent, x11-toolkits/qt5-gui, x11/qt5-x11extras,
x11-toolkits/qt5-widgets, x11-toolkits/qt5-declarative,
devel/qt5-linguisttools, print/qt5-printsupport, graphics/qt5-svg,
x11-toolkits/qt5-uiplugin, devel/qt5-uitools
```

Then, with Qt5 at 5.15.19:

- `x11/plasma6-plasma-integration at qt5` — builds, `EXIT=0` (previously
failed)
- `x11-themes/plasma6-breeze at qt5` — builds, `EXIT=0`
- `x11/plasma6-plasma` — packages and **installs cleanly at 6.6.6_1**,
all three Qt5 run-depends resolved

All 29 KF5 dependencies were already current; no port changes were
needed for the Qt5 rebuild itself.

### Adjacent findings (not addressed here)

- `Mk/scripts/sed_checked.sh` always runs `sed -i.bak` and never removes
the backups, so `devel/qt5-qmake` stages five stray `mkspecs/**/*.bak`
files and Q/A reports them as "missing from the plist". They are staged
but never packaged, so there is no user impact — cosmetic Q/A noise
only.
- mports Q/A reports ~16 "linked to ... but it is not declared as a
dependency" errors for `plasma6-plasma-integration at qt5`. These are the
transitive closure through `kio`/`kconfig`; FreeBSD declares none of
them either, and declaring them all would contradict how
`USE_KDE`/`USE_QT` propagate. Left matching upstream.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

https://claude.ai/code/session_01NSsgED5s7GPYJNb1HxuaU9

## Summary by Sourcery

Ensure the Plasma 6 meta port pulls in the complete set of Qt5
integration runtime dependencies.

Bug Fixes:
- Add the missing Qt5 KWayland integration runtime dependency so the
Plasma meta port installs all required Qt5 integration plugins.

Build:
- Bump the port revision for the dependency correction.

Signed-off-by: Lucas Holt <luke at foolishgames.com>
Co-authored-by: Claude Opus 5 (1M context) <noreply at anthropic.com>



To unsubscribe from these emails, change your notification settings at https://github.com/MidnightBSD/mports/settings/notifications