[MacPorts] #64005: cairo was updated to 1.17.4
MacPorts
noreply at macports.org
Fri Dec 24 19:03:23 UTC 2021
#64005: cairo was updated to 1.17.4
-------------------------+----------------------
Reporter: ryandesign | Owner: mascguy
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords:
Port: cairo |
-------------------------+----------------------
Comment (by mascguy):
Replying to [comment:6 ryandesign]:
> Oh. Could you point me to what those concerns were? I recently updated
glib2-devel to the next major version and was planning on updating glib2
as well, not aware there were problems with doing so.
The key concern was that we might break ports dependent on `glib2`. But so
long as we gradually update it - per the approach you're currently
following - there aren't any concerns, at least from my perspective.
> And what's the verdict with regard to why cairo was updated to an
unstable version?
Sorry for the delay on this. It may simply have been an oversight on my
part, but can't say for sure.
So, I'm currently rebuilding a number of direct dependents with Cairo
1.16.0, to see whether there are any issues. This list is only a small
subset of the ports dependent on Cairo, but it's a starting point:
* cairomm
* clutter
* cogl
* darktable
* frei0r-plugins
* grass7
* gstreamer1-gst-plugins-good
* harfbuzz-devel
* libchamplain
* libiodbc
* librsvg
* libspectre
* pango
* poppler
* py27-cairo
* py310-cairo
* py39-cairo
* rrdtool
* texlive-bin
* webkit2-gtk
But from a practical perspective: Given that Cairo 1.17.4 has been in use
for a few months now - without any known issues (I believe?) - is it worth
the effort of reverting to 1.16.0? (If nothing else, we'll need to rev-
bump every direct dependent.)
--
Ticket URL: <https://trac.macports.org/ticket/64005#comment:7>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list