pango 1.42.4: current stable release is 1.48.9

[PhilippImhof (Philipp Imhof)]

The version currently included in MacPorts is from August 2018. There have been quite a few improvements.

[kencu (Ken)]

a newer pango needs a newer glib2, and that has been our holdup.

[PhilippImhof (Philipp Imhof)]

I see, thanks for clarifying this. So we are basically stuck with a roughly 2 years old glib2 and therefore cannot upgrade pango (and probably many others). Will there be a solution in the near future?

[kencu (Ken)]

Ryan is in charge of glib2, and he has been reluctant to update it for a while now as it is a core port that promises widespread wreckage, and also until I fixed meson recently, would not build universal.

There has been a pull request in the queue for more than a year <​https://github.com/macports/macports-ports/pull/5808> to update glib2, but everyone is too overwhelmed, I guess, to take that project on.

There are several things I have wanted that needed a newer glib2, so the pressure is building. Just right now today, the whole world collapsed due to a gargantuan number of build failures of many ports on Apple Silicon due to their requirement for a header include for every function, and there about 5,000 broken ports due to that -- so the focus is on that issue right now.

Your best bet, if you really need it, is to build that PR on your own system and provide feedback to get 'er moving.

[evanmiller (Evan Miller)]

There is a pull request here that includes pango 1.48.9:

​https://github.com/macports/macports-ports/pull/11948

[mascguy (Christopher Nielsen)]

Updated version, as Pango 1.49.0 has just been released. Also updated the corresponding PR.

In the interim, if anyone's interested in testing with the latest release, it's available now via pango-devel. The latter was just updated to 1.49.0 as well.

[evanmiller (Evan Miller)]

I'm getting a pango-devel configure error on 10.4.11

:info:configure Executing:  cd "/opt/local/var/macports/build/_Users_emiller_macports.local_x11_pango-devel/pango-devel/work/pango-1.49.0" && /opt/local/bin/meson --prefix=/opt/local -Dxft=disabled --x-include=/opt/local/include --x-lib=/opt/local/lib --enable-introspection /opt/local/var/macports/build/_Users_emiller_macports.local_x11_pango-devel/pango-devel/work/pango-1.49.0 /opt/local/var/macports/build/_Users_emiller_macports.local_x11_pango-devel/pango-devel/work/build
:debug:configure system:  cd "/opt/local/var/macports/build/_Users_emiller_macports.local_x11_pango-devel/pango-devel/work/pango-1.49.0" && /opt/local/bin/meson --prefix=/opt/local -Dxft=disabled --x-include=/opt/local/include --x-lib=/opt/local/lib --enable-introspection /opt/local/var/macports/build/_Users_emiller_macports.local_x11_pango-devel/pango-devel/work/pango-1.49.0 /opt/local/var/macports/build/_Users_emiller_macports.local_x11_pango-devel/pango-devel/work/build
:info:configure usage: meson [-h] {setup,configure,dist,install,introspect,init,test,wrap,subprojects,help,rewrite,compile} ...
:info:configure meson: error: unrecognized arguments: --x-include=/opt/local/include --x-lib=/opt/local/lib --enable-introspection
:info:configure Command failed:  cd "/opt/local/var/macports/build/_Users_emiller_macports.local_x11_pango-devel/pango-devel/work/pango-1.49.0" && /opt/local/bin/meson --prefix=/opt/local -Dxft=disabled --x-include=/opt/local/include --x-lib=/opt/local/lib --enable-introspection /opt/local/var/macports/build/_Users_emiller_macports.local_x11_pango-devel/pango-devel/work/pango-1.49.0 /opt/local/var/macports/build/_Users_emiller_macports.local_x11_pango-devel/pango-devel/work/build
:info:configure Exit code: 2

It looks like this is an issue with Meson being pegged at 0.55.3 on that platform.

[mascguy (Christopher Nielsen)]

Replying to evanmiller:

I'm getting a pango-devel configure error on 10.4.11

It looks like this is an issue with Meson being pegged at 0.55.3 on that platform.

Does anyone know whether newer Meson releases have a hard dependency on macOS 10.5 and later? Or is this resolvable via a patch, and/or additions to legacy-support?

[mascguy (Christopher Nielsen)]

P.s. If it's fixable, I nominate Evan to work on it.

;-)

[evanmiller (Evan Miller)]

P.s. If it's fixable, I nominate Evan to work on it.

Greatly honored by such a nomination :-)

Actually: have you tried compiling +x11? It looks like that variant has some outdated logic with the configure args. The Meson version could be a red herring.

[evanmiller (Evan Miller)]

My bad – I had an outdated Portfile from an earlier version of the pull request on my machine. Please disregard the error message about unrecognized arguments passed to Meson.

[kencu (Ken)]

No meson version since forever works on Tiger. TBH we are quite lucky to have anything working, as nobody else has any meson for Tiger.

I patched some fairly ugly looking workarounds that I am not proud of to make it work, for a while at least.

It's pegged because it breaks almost every update and needs to be redone.

[ryandesign (Ryan Carsten Schmidt)]

pango used to follow the gnome even/odd version standard, where the second number in the version number determines whether the release is stable or development, e.g. 1.40.x would be stable while 1.41.x would be development. If pango still follows that method, then the latest version to which the port could be updated at this time is 1.48.9, as the livecheck currently says. ​gnome stopped using that version numbering standard recently. If pango has followed gnome in no longer using that standard, then we can update to 1.49.x, but I could not find anything stating that they have made such a change; if you can find confirmation one way or the other, please share it here.

[mascguy (Christopher Nielsen)]

Replying to ryandesign:

pango used to follow the gnome even/odd version standard, where the second number in the version number determines whether the release is stable or development, e.g. 1.40.x would be stable while 1.41.x would be development. If pango still follows that method, then the latest version to which the port could be updated at this time is 1.48.9, as the livecheck currently says. ​gnome stopped using that version numbering standard recently. If pango has followed gnome in no longer using that standard, then we can update to 1.49.x, but I could not find anything stating that they have made such a change; if you can find confirmation one way or the other, please share it here.

I'll do some quick research, but my guess is that you're likely right about the version numbering scheme. (Juggling a few too many interdependent port updates at the moment, and completely forgot about pango-devel using livecheck type gnome-with-unstable. Doh!)

Assuming that's still the case, I'll downgrade pango-devel. Though only after I've rebuilt key ports like harfbuzz-devel, and some others, to ensure all is well.

More to follow.

[mascguy (Christopher Nielsen)]

Update: It looks like Pango releases still follow the stable/unstable version numbering scheme. A commit to downgrade pango-devel to follow momentarily.

[Christopher Nielsen <mascguy@…>]

In d0557cd6f5d4779efdcc0ccbe482a4247c9a1164/macports-ports (master):

pango-devel: downgrade to latest stable release
See: #61814

[devernay (Frédéric Devernay)]

@macsguy do we have an ETA for the upgrade of the pango package itself?

Or does in depend on a working meson on Tiger (@kencu)?

[devernay (Frédéric Devernay)]

hum meson seems to be fixed already on Tiger #63488

[evanmiller (Evan Miller)]

pango-devel builds just fine on Tiger/PPC now. @kencu may want to test on Tiger/i386 and Leopard/PPC before giving his blessing.

[Christopher Nielsen <mascguy@…>]

In 90a23d95aea607835f72aab573ee21f9609cab64/macports-ports (master):

pango: update to 1.49.0

Closes: #61814