Opened 14 months ago

Last modified 11 months ago

#68530 new enhancement

scribus-devel: move to 1.7.x and Qt6 or introduce a new scribus-upstream

Reported by: barracuda156 Owned by:
Priority: Normal Milestone:
Component: ports Version: 2.8.1
Keywords: bigsur, monterey, ventura, sonoma Cc: ryandesign (Ryan Carsten Schmidt)
Port: scribus-devel

Description

Not sure if there is a need in Qt5-based version, since it requires very new Qt5 (5.14.0), which is broken on older systems anyway, and those use Qt4-based scribus. But if there is such a need, then it is desirable to introduce scribus-upstream using Qt6.

Change History (4)

comment:1 Changed 14 months ago by ryandesign (Ryan Carsten Schmidt)

It is not customary to have ports with names ending with "upstream". We typically only have one port for the stable version. Sometimes, as with scribus, we offer a second port for a newer development version.

Scribus is an unusual case because the project has taken a very long time between releases, to the point of not wanting to accept bug reports or fixes for the stable version.

Upstream will release scribus 1.6.0 as the new stable version soon (the developer told me it would be this month), at which point customarily we would update the scribus port. That would make it use qt5 and cause problems for old systems that can't use qt5.

If there is a desire to keep support for qt4 systems, then a different strategy should be used where we switch to versioned ports: scribus1.4, scribus1.6.

comment:2 Changed 14 months ago by barracuda156

My ticket was rather about switching to Qt6 for the -devel version, but yes, absolutely, Qt4-based version is necessary. IMO it is more intuitive to rename it to scribus-legacy, but versioned port is also okay.

  1. S. Versioned ports normally imply that a simultaneous installation may be desired. Perhaps no one would need an older scribus as long as a newer builds and works. Qt4-based version is needed only for systems where Qt5/Qt6 are broken.
Last edited 14 months ago by barracuda156 (previous) (diff)

comment:3 Changed 11 months ago by MrB74

I announced Scribus 1.6.0 release yesterday, so this can be progressed by replacing the standard scribus package by 1.6.0 which is qt5 based. We have not yet released a 1.7.0 version which is Qt6 based which would fit the scribus-devel package.

comment:4 in reply to:  3 Changed 11 months ago by barracuda156

Replying to MrB74:

I announced Scribus 1.6.0 release yesterday, so this can be progressed by replacing the standard scribus package by 1.6.0 which is qt5 based. We have not yet released a 1.7.0 version which is Qt6 based which would fit the scribus-devel package.

We cannot replace it with Qt5-based version since Qt5 is broken on a number of platforms. We can, of course, use versions conditionally on the OS, pegging those which need Qt4 to the last Qt4-supporting one.

Note: See TracTickets for help on using tickets.