I see the macports.conf lets you configure rsync_dir, the path of the tarball that selfupdate uses to fetch the base files. Is it possible to distribute the master branch, or a beta branch, on the mirrors so selfupdate could keep you up to date on those releases instead? Something like how Chrome has its beta and canary channels?
David Gilman :DG< On Mon, Aug 18, 2025 at 10:19 AM Joshua Root <[email protected]> wrote: > The MacPorts Project is pleased to announce the release of version > 2.11.5. This is a bugfix release with small changes only. See the > ChangeLog [1] for the list of changes. > > If you already have MacPorts installed, the preferred method for > updating is to run: > > sudo port selfupdate > > For new installs, there are also package installers available for macOS > versions ranging from macOS 15 Sequoia all the way back to 10.5 at [2]. > The source is also available as tarballs compressed with gzip or bzip2, > or from the git tag [3]. > > Detached PGP signatures for the disk images, packages and source > tarballs have been made with my key, which is available on the > keyservers and my MacPorts wiki page [4], the fingerprint being: > > 0x01FF673FB4AAE6CD: C403 7936 5723 6DCF 2E58 0C02 01FF 673F B4AA E6CD > > Josh > (on behalf of the MacPorts Port Managers) > > [1] <https://github.com/macports/macports-base/blob/release-2.11/ChangeLog > > > [2] <https://www.macports.org/install.php> > [3] <https://github.com/macports/macports-base/releases/tag/v2.11.5> > [4] <https://trac.macports.org/wiki/jmr> > >
