Hi Marcell, First of all, I just want to say I really appreciate all the work you've been doing with your KDE/Qt requests! I've been extremely busy lately, so it's been hard to keep up with everything; I'm hoping to implement the rest of your suggestions this week. When it comes to the Qt5 stuff, I see your point that a -git version is no different from the one in the official repos at this point, when it comes to features. That said, I think there's still value in keeping the PKGBUILDs around, in case people want to build it from source with custom flags, or simply to support old software when Qt5 inevitably gets dropped from the official repos. Similarly, Qt4 is still around in the AUR. So I would suggest that we wait for Qt5 to be moved from the official repos to the AUR (without the -git suffix), and then I can submit merge requests from the -git versions to the non -git versions. What do you think?
Best regards, João On Monday, 13 November 2023 14:45:50 WET you wrote: > Only in response to my deletion request, maintainer has changed the source to > KDE's backport maintenance fork. > > But my original argument for dropping this from AUR still holds: it's not use > to keep this package, as Arch extra repo's stable equivalent also gets bumped > frequently to build from new commits published to same maintenance branch. > Qt5 is EOL, and soon won't receive any backported patches whatsoever. The > stable package should be enough to have around, as long as there are reverse > dependencies. > > On 20 October 2023 17:35:09 GMT+02:00, [email protected] wrote: > >MarsSeed [1] filed a deletion request for qt5-translations-git [2]: > > > >Not useful to keep this package. > > > >Qt5 is EOL since May 2023. > > > >This PKGBUILD currently builds from upstream's Qt5 branch, which is > >typically behind the source used by the stable PKGBUILD in extra repo. > >Qt devs delay pushing Qt5 patches to the public repo by one year, > >whereas the KDE project cherry-picks and backports most of the > >important commits accepted by Qt Group for Qt5 but not yet publicly > >pushed. > > > >Therefore the extra repo build is better for users and developers > >alike, because it is based on newer code which has less bugs. > > > >As a consequence of all this, the extra/qt5* packages are quite like > >git VCS packages. > > > >[1] https://aur.archlinux.org/account/MarsSeed/ > >[2] https://aur.archlinux.org/pkgbase/qt5-translations-git/ > >
