#58926 closed update (wontfix)
pango-devel: WIP to update to 1.44.6
Reported by: | kencu (Ken) | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | ryandesign (Ryan Carsten Schmidt), MaddTheSane (C.W. Betts), dbevans (David B. Evans) | |
Port: | pango, pango-devel |
Description
There are some significant changes in the more recent pango ports, and the build is quite different; uses meson
, different configure args, etc.
The attached Portfile builds the current version as of now (1.44.6). Because our current glib2 is too old, it also builds the current version of that (2.61.3) which obviously we'll have to separate out as a separate port for glib2.
There is tweaking to be done, but I thought it might at least get the ball rolling for updating to a current pango.
Hope you find this a starting point.
Attachments (2)
Change History (9)
Changed 5 years ago by kencu (Ken)
Attachment: | pango-1.44.6-WIP-Portfile.diff added |
---|
Changed 5 years ago by kencu (Ken)
Attachment: | pango-1.44.6-WIP-Portfile added |
---|
comment:1 Changed 5 years ago by kencu (Ken)
comment:2 Changed 5 years ago by kencu (Ken)
Type: | defect → update |
---|
comment:3 Changed 5 years ago by MaddTheSane (C.W. Betts)
Cc: | MaddTheSane added |
---|
comment:4 Changed 5 years ago by kencu (Ken)
Resolution: | → wontfix |
---|---|
Status: | new → closed |
comment:5 Changed 5 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | dbevans added |
---|
pango and glib2 should be updated to newer versions. But because of the new build system and the anticipated complexity and time involved in figuring out how to do that, I have not attempted to do so, and have no plans to do so at this time. If others want to pursue it and deal with any resulting problems, please do.
comment:6 Changed 5 years ago by MaddTheSane (C.W. Betts)
The outdated Pango is still causing crashes in FontForge.
comment:7 Changed 5 years ago by ryandesign (Ryan Carsten Schmidt)
Sorry, I did not know about that. I missed the notification for #57249.
getting the tests to work requires
ninja test
in the build directory, so something like this in the Portfile should do it I think (not actually tested in the Portfile)