Qwt is currently built with Qt5 - should I mark the package as out-of-date?
Hi all, Sorry if this is a naive question, but qwt <https://archlinux.org/packages/extra/x86_64/qwt/> is currently being built with Qt5, which is nearing end-of-life <https://endoflife.date/qt>, while Qt6 has been out for a while. I'd like for qwt to be built with Qt6, but I'm not sure if this means the package is out-of-date strictly speaking, so I figured I'd ask here before marking the package as such. What's the right way to deal with this? Best, - Peyton
On Wed, 29 Mar 2023, Peyton Murray wrote:
Hi all,
Hi Peyton,
Sorry if this is a naive question, but qwt is currently being built with Qt5, which is nearing end-of-life, while Qt6 has been out for a while. I'd like for qwt to be built with Qt6, but I'm not sure if this means the package is out-of-date strictly speaking, so I figured I'd ask here before marking the package as such. What's the right way to deal with this?
Personally, I would rather open a bug for this. Reasons: * if there are any obstacles regarding building with Qt6, a bug is more appropriate to bundle issues, discussions, efforts, ... * technically speaking, the package is not outdated (yet) * If for whatever reason qt5 got removed from the repositories and the package still was not rebuilt, it would *definitely* be a bug. * If for whatever reason, you're wrong, the maintainer can close your bug and tell you (and everyone else), what's wrong, in the reason.
Best, - Peyton
regards, Erich
Looks like this should be treated as an upstream qwt issue. Thanks for the input! On Wed, Mar 29, 2023 at 11:27 PM Erich Eckner <arch@eckner.net> wrote:
On Wed, 29 Mar 2023, Peyton Murray wrote:
Hi all,
Hi Peyton,
Sorry if this is a naive question, but qwt is currently being built with Qt5, which is nearing end-of-life, while Qt6 has been out for a while. I'd like for qwt to be built with Qt6, but I'm not sure if this means the package is out-of-date strictly speaking, so I figured I'd ask here before marking the package as such. What's the right way to deal with this?
Personally, I would rather open a bug for this. Reasons:
* if there are any obstacles regarding building with Qt6, a bug is more appropriate to bundle issues, discussions, efforts, ...
* technically speaking, the package is not outdated (yet)
* If for whatever reason qt5 got removed from the repositories and the package still was not rebuilt, it would *definitely* be a bug.
* If for whatever reason, you're wrong, the maintainer can close your bug and tell you (and everyone else), what's wrong, in the reason.
Best, - Peyton
regards, Erich
El mié, 29-03-2023 a las 22:32 -0700, Peyton Murray escribió:
Sorry if this is a naive question, but qwt is currently being built with Qt5, which is nearing end-of-life, while Qt6 has been out for a while. I'd like for qwt to be built with Qt6, but I'm not sure if this means the package is out-of-date strictly speaking, so I figured I'd ask here before marking the package as such. What's the right way to deal with this?
No. Marking a package as out-of-date is only to indicate that a new version of the package is available. In any case, from what they indicate on their page[1], it is not compatible with Qt6 (Platforms section): Qwt 6.2 might be usable in all environments where you find Qt. It is compatible with Qt 4.8 and all Qt5 versions. [1]: https://qwt.sourceforge.io/ -- Óscar García Amor | ogarcia at moire.org | http://ogarcia.me
participants (3)
-
Erich Eckner
-
Peyton Murray
-
Óscar García Amor