Nice one! 🙌 -- James Mills / prologic Join Yarn.social today! The only decentralised social media that respects your privacy and freedoms! E: prologic@shortcircuit.net.au W: prologic.shortcircuit.net.au Blog: Read my Blog Yarn: @prologic@twtxt.net On Mon, Jan 6, 2025 at 8:42 AM Matt Housh via CRUX <crux@lists.crux.nu> wrote:

Greetings, all,

There is a test ISO available for the upcoming CRUX version 3.8. It is *NOT* released or finalized yet but please feel free to test it and report any ISO- or setup-specific issues.

It can be found here: https://crux.nu/files/rc/crux-3.8-rc3.iso https://crux.nu/files/rc/crux-3.8-rc3.md5 https://crux.nu/files/rc/crux-3.8-rc3.sha256

Regards, Matt

_______________________________________________ CRUX mailing list -- crux@lists.crux.nu To unsubscribe send an email to crux-leave@lists.crux.nu

Hello all, Great to hear that a new official ISO is in the works. Kudos to the core team for all their hard work! Matt Housh via CRUX <crux@lists.crux.nu> wrote:

report any ISO- or setup-specific issues.

Earlier today in the #crux-social channel I tried to flesh out some possible uses for rename_packages() in the 3.8 setup-helper. The transition from 3.7 to 3.8 gives us the chance to reconsider the port names that refer to an outdated soversion. For example, my contrib ports glibmm and pangomm do not mention the soversion in their names, which forced the GTK4 counterparts of these libraries to take more cumbersome names: tagged with 2.68 and 2.48, respectively. Because the development is more active in GTK4 than in GTK3, these soversion-tagged contrib ports are now at versions 2.82 and 2.54, which might be confusing to users who don't know the history. I'd be happy to free up the untagged names glibmm and pangomm, letting them be used for their GTK4 counterparts. But if a successor to GTK4 ever emerges, then we run into the same problem. In my brainstorming on IRC, I had the idea to preemptively tag any port that targets a specific toolkit version. Maybe we could add to setup-helper some lines like rename_packages glibmm:glibmm-gtk3 rename_packages pangomm:pangomm-gtk3 rename_packages glibmm-2.68:glibmm-gtk4 rename_packages pangomm-2.48:pangomm-gtk4 which would clarify the connection between the name and the ports that claim it as a dependency. Such a change would obviously require us maintainers to fix the dependency lines in some Pkgfiles. But if these fixes are rolled out with the CRUX 3.7 -> 3.8 transition, it will be a more seamless experience for everyone. There might be other ports that could benefit from the rename_packages function in setup-helper. I don't mean to single out the GTK4 libraries; these were just the ports that came to mind first. Moving forward, preemptive tagging to highlight the toolkit version (as is done for the qt6-* ports) could become a more common practice, sparing us the agonizing renaming decisions when the world moves on from older toolkits. Cheers, John