Re: bsdisks switched unconditionally to QT6

On Mon, 17 Jun 2024 06:41:04 -0400
"Jason E. Hale" <jhale@freebsd.org> wrote:

> On Sun, Jun 16, 2024 at 10:14 AM Michael Butler
> <imb@protected-networks.net> wrote:
> >
> > I have KDE5 installed; this pulls in devel/kf5-solid which has a
> > dependency on sysutils/bsdisks like so ..
> >
> > imb@d5540:/usr/ports/devel/kf5-solid> less Makefile
> > PORTNAME=       solid
> > DISTVERSION=    ${KDE_FRAMEWORKS_VERSION}
> > CATEGORIES=     devel kde kde-frameworks
> >
> > MAINTAINER=     kde@FreeBSD.org
> > COMMENT=        KF5 hardware integration and detection
> >
> > RUN_DEPENDS=    bsdisks:sysutils/bsdisks
> >
> > USES=           bison cmake compiler:c++11-lib kde:5 qt:5 tar:xz
> >
> >   [ .. snip .. ]
> >
> > But after ..
> >
> > commit 91ee9ec8e0dbfa97b298e6498900938e71762837
> > Date:   Tue May 21 21:38:37 2024 +0300
> >
> >      sysutils/bsdisks: Switch to Qt 6
> >
> >      PR:             279168
> >
> >   .. I now have to build and maintain *both* versions of QT.
> >
> > This makes no sense to me. Can this be fixed to build with just the
> > installed version?
> >
> >         Michael
> >
> 
> Qt5 is on its last leg and is in the process of being phased out, as
> official support for even paying commercial consumers has less than a
> year left. We at kde@ are actively trying to eliminate Qt5
> dependencies as much as possible in the meantime to facilitate the
> total transition to Qt6, so please forgive our dust. During this
> transitionary period, users will likely have Qt5 and Qt6 modules
> installed simultaneously. This entails many hours of *volunteer* work
> from just a few people and we respectfully ask our users to please be
> patient during the transition.
> 
> - Jason

Fisrt of all, thanks for your hard work for transition.

Just IMHO, having components of Qt5 and Qt6 is (excluding too huge
to build qt*-webengine port) is not at all a problem.

But some ports (sorry, lost track with actually which was) seems to be
conflicting each other.

This would avoid accepting such a coexistense.
So, is it easily possible to rename Qt5 side of conflicting file as
something like *-qt5 and fix their dependencies (Qt5 apps) to use the
modified name?

IMHO, this kind of conflicts could be treated upstream in the future
(i.e. future Qt7 decides to name such files as *-qt7 at the first
place), so renaming Qt6 side would be just a mess.

Regards.

-- 
Tomoaki AOKI    <junchoon@dec.sakura.ne.jp>