ティージェーグレェ on Nostr: You are too kind! Also, you are very welcome. I could be doing a lot better with ...

You are too kind! Also, you are very welcome.

I could be doing a lot better with regards to maintaining Got -portable in MacPorts. This Trac issue for example sometimes keeps me up at night:

https://trac.macports.org/ticket/71820

In theory, I could dig up some older Mac laptops I have in storage; but day to day I basically just have one system at my disposal and keep it more or less in alignment with Apple's public equivalent to -RELEASE.

Before my car was broken into (again) last summer and thieves made off with more of my material possessions, I had three laptops more readily available, one also effectively running -CURRENT (or whatever beta software Apple was making public) and another running OS X El Capitan (much older, but not as old as OS X Leopard which MacPorts also supports) + VMs for some other stuff so I could more easily test things on older versions of macOS/OS X.

At the moment I'm doing less due diligence and other MacPorts users are clearly noticing some breakage on older OS versions and I don't really have the where with all to help them out as much as I would like.

I am not sure when my circumstances will change (I will be doing some storage unit stuff later today and again, could in theory dredge up one of my much older laptops, but my living situation/car is in an even worse state presently and I'm never trying to make myself more of a target for thieves so those misgivings aren't likely to go away any time soon).

Hopefully things in my life will ease up sooner than later? Even better would be if other MacPorts contributors submit improvements to Got for older versions of OS X where my own coverage is presently substandard.

It could, in theory, probably be as easy as adding a local patch for older OS versions, or as I suggested in the Trac issue, maybe leveraging MacPorts' legacy-support/legacy-support-devel tools which kind of provide a more generalized set of similar things, but I can't really do much to test such efforts for the time being.

There are also some realities that the MacPort for Got doesn't really deal with the daemon stuff (I had submitted a "variant" to enable it when gotwebd was introduced, but got some push back in that effort from other more experienced MacPorts contributors and I am hardly an expert within that project and decided to err on the side of caution/abstention/omission). Realistically, that's maybe not a bad thing given that macOS has such aggressive power saving defaults, that without use of /usr/bin/caffeinate it's ill advised for server/daemon types of use IMHO.

I'm sure I am an outlier, but my overall vibe with macOS is that it's kind of like "My First UNIX" (parodying the "My First Sony" branding) and MacPorts is an OK, if not amazing viable alternative to /usr/ports. IMHO, it would really behoove more seasoned sorts to level up and start working with FreeBSD and OpenBSD and such more directly if they want to get serious about UNIX and libre/free open source software. So part of me is reticent if not outright reluctant to make MacPorts contributions outstanding, when I think it's probably a better use of skills and talents to toil more upstream when possible.

To that end, I really should be thanking you and the other Game of Trees developers! The mailing list is still a continual source of inspiration of setting a good example of collaboration.

I'm also still very excited about gothub and seeing how that evolves!

Having written as much, seeing your recent post mentioning gotsysd and gothub funding is reminding me that I thought I had made an attempt to contribute to the funding, but never saw a deduction from my credit card and even emailed opencollective.com back in June of last year after they sent me an "ACTION REQUIRED" email regarding my attempt to donate, and I never received word back after that. Hopefully that experience was unusual, but it makes me wonder if other potential donors maybe faced similar challenges?