[MacPorts] #69748: glib2, glib2-devel @2.80.0 conflicts with gobject-introspection

[MacPorts]

#69748: glib2, glib2-devel @2.80.0 conflicts with gobject-introspection
-------------------------------------------------+-------------------------
  Reporter:  barracuda156                        |      Owner:  mascguy
      Type:  defect                              |     Status:  assigned
  Priority:  Normal                              |  Milestone:
 Component:  ports                               |    Version:  2.9.3
Resolution:                                      |   Keywords:
      Port:  glib2, glib2-devel, gobject-        |
  introspection                                  |
-------------------------------------------------+-------------------------

Comment (by eirnym):

 Replying to [comment:27 mascguy]:
 > Replying to [comment:26 eirnym]:
 > > According to internet search (google, ddg, etc), all package systems
 has been failed with this change in glib2/gobject-introspection. I believe
 core developers thought that system has already gobejct-introspection
 library installed and they didn't check other applications.
 > >
 > > Could somebody ping core developers? I believe it's worth a while to
 let them know what mess they have been made.
 >
 > Let's try to avoid criticizing upstream. My only complaint is that the
 release notes didn't shout this out more clearly, as it's not immediately
 clear from either project how much things changed for 1.80.x. But
 otherwise, Linux distribution and such seem to have this figured out, so
 this is on me.


 I respect your point, but I see exactly the same discussion in just every
 distro for this particular version (as ddg/google shows in their results).
 Linux distributions has "figured this out", as 99% of users will just
 download pre-built binaries, and other 1% will read mailing lists of
 respective distributions. If port/package maintainters won't notify
 developers, there's a chance, that they won't notice it at all.

 The dependency cycle clearly be a result of an improper refactoring, when
 tools were already pre-installed on all machines and developers were just
 trying to rebuild libraries even on CI. I see it as a misuse of current
 build environment and testing of upgrade only without a package manager
 (e.g. make install) vs clean install.

-- 
Ticket URL: <https://trac.macports.org/ticket/69748#comment:48>
MacPorts <https://www.macports.org/>
Ports system for macOS