KDE Gear 24.12.0 packages available for packagers
Tobias Leupold
tl at stonemx.de
Fri Dec 6 16:14:04 GMT 2024
E-Mail von Heiko Becker vom Freitag, 6. Dezember 2024, 13:50:51 MEZ:
> On Friday, 6 December 2024 12:08:46 CET, Christophe Marin wrote:
> > Slightly related to this release, packagers need to know what to do with
> > packages depending on Qt 5 and marble:
> >
> > - kgeotag (1.6.0 release only supports KF5/Qt5)
> > - kphotoalbum (5.13 release only supports KF5/Qt5, but the
> > marble dependency
> > is optional)
> > - kexi (no release for the past 5 years)
>
> Just to add some piece of information here, because one could get the
> impression that Marble is a hard dependency of kexi. Actually it's optional
> as well. And while the current release searches for (Kexi)Marble, the
> respective subdir is commented out (and still is in git master), so I'd say
> it doesn't depend on marble at all the moment.
>
> > - kreport (no release for the past 5 years)
>
> It's an optional dependency there, too.
>
> > I'm not expecting users will notice if we drop kexi and kreport, but
having
> > solutions for the other ones before the 24.12 release would be nice.
>
> Seems we're not particular good at foreseeing such things...
> Six days isn't much time, but I added Tobias in CC to hear if a soonish
> release of a Qt6-based kgeotag may be realistic.
I just talked to Johannes Zarl-Zierl (KPhotoAlbum's maintainer), and we both
agree that it would be no problem if we released Qt6/KF6 KPhotoAlbum and
KGeoTag now. We depend on Marble 24.11.70 in current git master, which was the
first tag to support Qt 6 IIRC. And when the 24.12.0 release is out,
everything is still fine. The code should be ready for both projects.
I think this way, distributors can package both the new KPhotoAlbum and
KGeoTag versions, and update them along with Marble so that nothing is
blocked.
Would this be okay? I'd try to do the release tomorrow, asap.
Cheers, Tobias
> Regards,
> Heiko
More information about the release-team
mailing list