Ah well, fuck. I'm essentially almost done as well, although I didn't know about bootstrapping. I got glib2 building at 2.86.3, glib2-devel at 2.87.2, gobject-introspection (and -devel) @ 1.86.0 and glibmm (and devel) @ 2.86.0. Was now just tackling py-gobject3 and was then gonna look into glib-networking.
Would I be missing anything still? Gregorio Litenstein Goldzweig Médico Cirujano • Fono: +56 9 96343643 • E-Mail: [email protected] On 13 Feb 2026 13:21 -0300, Renee Otten <[email protected]>, wrote: > I have finished an update for glib2 and friends yesterday (including proper > bootstrapping of the ports) which is needed for a new port I want to add, > just didn’t push a PR yet. I started opening some PRs for a few other > packages first, but can push an PR with the updates to the “-devel” ports > shortly so you don’t have to redo the same work. You’ll see a PR in the next > hour or so. > > I am not using “gnome-music” an any of the other old packages and totally > agree with you we cannot block updates forever just to keep old cruft working. > > Renee > > > > On Feb 13, 2026, at 11:10 AM, Gregorio Litenstein <[email protected]> > > wrote: > > > > Hi everyonne. I'm currently working to update glib2 and its extended family. > > In doing so, I noticed a note inside py-gobject3 about "older ports" > > needing the ability to build with python 3.6. > > > > I ran `port list depends:py36-gobject3`, and got gnome-music and > > gnome3-core for results. > > > > Regarding the former, the gnome-music port is currently version 3.24.2, > > released in may 2017, while the current version, as of a couple of months > > ago, is 48.3. > > Regarding gnome3-core, we have 3.26.2, release in november 2017. GNOME 3 > > went EOL five years ago, after 3.38.0. > > > > So... is anybody actually using these things? I see they have been > > maintained relatively recently with chores and menial updates, but they > > haven't actually beenn updated in years, and I thik it'd be ridiculous to > > hold important updates to big libraries because of them. > > > > For now, I think I won't touch them, but I really think they should be > > removed, especially if they prove to be blockers for updating py-gobject3. > > > > All the best. > > > > > > Gregorio Litenstein Goldzweig > > Médico Cirujano > > > > > > • Fono: +56 9 96343643 > > • E-Mail: [email protected] > > >
