rsync:// ports.tar URL in the Guide.

[soulne4ny (Alexey Luchko)]

​https://guide.macports.org/#development.local-repositories

The url rsync://rsync.macports.org/macports/release/tarballs/ports.tar [default] seems to be outdated.

[mf2k (Frank Schima)]

Correcting my comment. Yes, the extra /macports needs to be removed.

[mf2k (Frank Schima)]

That is also the value in sources.conf.default.

[ryandesign (Ryan Carsten Schmidt)]

No, it is correct as written.

Prior to two years ago, our master rsync server was hosted by macOS forge and was only used by MacPorts, so we had the entire rsync namespace available to us. We used rsync modules called release, trunk, distfiles, packages. We also had a macports rsync module which encompassed all four of the other modules.

As of two years ago, macOS forge shut down, and our master rsync server moved to FAU, which added our rsync content to an existing rsync server already hosting other rsync modules. As such, we deprecated the formerly separate release, trunk, distfiles and packages rsync modules and updated the guide and config files to recommend using the combined macports module instead. The old modules are still being provided by FAU for compatibility, but they would like to remove those modules eventually. See #54056.

[soulne4ny (Alexey Luchko)]

I was under impression it all is on github now. My config states file:///opt/local/var/macports/sources/github.com/macports/macports-ports/ as default. Which surprises me.

Sorry for misleading report.

[ryandesign (Ryan Carsten Schmidt)]

MacPorts development did move from Subversion to GitHub 2 years ago, but as before, our primary means of distributing the ports tree is rsync. Alternate methods are available, especially for users whose networks block rsync traffic; you've evidently configured your sources.conf to use one of those alternate methods.