I've released the -portable version of #gameoftrees, 0.112
This is merely tracking got-0.112 and has no -portable changes in it at all.
Usual details, etc., can be found here:
@teajaygrey -- if you'd like me to mirror the -portable releases somewhere for you to access, let me know.
ティージェーグレェ
in reply to Thomas Adam • • •Thanks! I can access the -portable releases A OK personally.
The snag is MacPorts' use of GitHub requiring a mirror that GitHub Actions can access when it runs its Continuous Integration checks.
If you can manage something, that would be awesome!
Though I also documented my thoughts here:
trac.macports.org/ticket/72492
AFAIK, MacPorts does has some mirroring infrastructure taking the form of hostnames in the *.distfiles.macports.org subdomains, e.g.
ywg.ca.distfiles.macports.org/…
bos.us.distfiles.macports.org
ykf.ca.distfiles.macports.org/…
etc.
However, I know next to nothing about how those operate?
My best guess is it's semi-automated and populated once a Portfile has been updated?
Basically, from my limited understanding, since MacPorts kind of combines the functionality of /usr/ports and pkg (for lack of a better description) it defaults to seeing if it can find a pre-compiled build of a given MacPort when an install is requested.
So, if it fails to fetch an archive $(portname){$version}.darwin_($version).($architecture).tbz2 from the packages mirrors (e.g. packages.macports.org/) then it will begin to search for the tarball via the *.distfiles.macports.org mirrors and build from source.
I wish I were more of a MacPorts' expert; but I get the impression maybe others might know if there's a way to use the *distfiles.macports.org mirrors for got -portable tarballs? Hopefully at least!
It's a strange "community" for lack of a better description (and I'm pretty strange as a given even if I weren't attempting to be helpful).
#72492 (got: update to 0.112) – MacPorts
trac.macports.orgThomas Adam
in reply to ティージェーグレェ • • •ティージェーグレェ
in reply to Thomas Adam • • •Ah, yeah, the MacPort will definitely need something. Admittedly, I have attempted (so far, unsuccessfully) to see if there's interest from MacPorts contributors to move away from GitHub.
If you can provide a mirror that would be awesome!
Though, I am still wondering if MacPorts' own distfiles mirrors can maybe be leveraged somehow? I don't anticipate anyone has replied to the Trac issue I opened with such pontifications yet.
ティージェーグレェ
in reply to Thomas Adam • • •As an addendum to snac.bsd.cafe/teajaygrey/p/174… (which maybe you didn't see because now I see it doesn't seem as if you were CCed? Maybe my fault! Whoops!)
It looks as if my hopes that the *distfiles.macports.org mirroring infrastructure might be able to be utilized somehow were for naught based on this response:
lists.macports.org/pipermail/m…
Anyway, there's no rush! I appreciate any efforts you may be able to make to help facilitate things downstream (and you already do a lot and thank you for that too!).
Part of me is even wondering if I might be able to use something like my neocities.org account for mirroring the tarballs, but I liked your suggestion in the Pull Request about signing things too. So do whatever feels right, this doesn't need to be a "right now" kind of stopgap break/fix fire drill. After all, in UTC it's already Friday and you know what seasoned ops sorts say about code pushes on Fridays! ;)
Mirroring (Was: Re: MacPorts rsync is broken?)
lists.macports.orgティージェーグレェ
2025-05-15 23:44:56
ティージェーグレェ
in reply to Thomas Adam • • •For the time being, another MacPorts' contributor had the clever idea to utilize FreeBSD's mirror:
github.com/macports/macports-p…
got: update to 0.112 by aeiouaeiouaeiouaeiouaeiouaeiou · Pull Request #28464 · macports/macports-ports
GitHubThomas Adam
in reply to ティージェーグレェ • • •Why are we going round in circles on this?
I said I'd provide you a mirror.
Here it is:
xteddy.org/mirror/got-portable…
When I release a -portable version, it will appear there.
This process is automated, currently checks once a day, which means even if I'm not the one doing a -portable release, that will always be kept up to date. Although since I am doing -portable releases, this mirror will update as soon as I upload to got-www.
The "problem" in using FreeBSD-ports is you're at the mercy of when the maintainer is going to update that port, which could be a while, depending when they're able to update it, etc.
HTH!
ティージェーグレェ
in reply to Thomas Adam • • •Thomas Adam
in reply to ティージェーグレェ • • •ティージェーグレェ
in reply to Thomas Adam • • •I'll definitely keep you in the loop!
I tried making changes locally; but since aeiouaeiouaeiouaeiouaeiouaeiou's 0.112 PR (github.com/macports/macports-p…) was merged, now MacPorts' mirrors have the 0.112 tarball from FreeBSD's mirrors and even when I change the Portfile locally to reflect your mirror, it seems to want to grab the tarball from the pre-populated MacPorts mirrors (I tried to see if there was some way to get MacPorts to ignore that, but if such a thing is possible, it doesn't seem well documented in the port manpage).
I'm guessing it will function OK, but it looks as if I won't be able to actually test it until 0.113 is released and the corresponding tarballs (which will not have yet been cached by MacPorts and their mirrors as it will not yet be updated [presumably! Unless someone submits a Pull Requests and merges it without me noticing, which seems, less likely?]) are available on you mirror.
got: update to 0.112 by aeiouaeiouaeiouaeiouaeiouaeiou · Pull Request #28464 · macports/macports-ports
GitHub