On 2016-11-12 22:30, Ryan Schmidt wrote: > We do actually have a "trunk" rsync directory. Isn't the purpose of > that to allow users of master to selfupdate using it? I've never > tried it.
Even if you change the rsync_dir in macports.conf, the version on master is always 2.3.99. This is the same version you already have installed, so it will not attempt an upgrade (unless being forced). >> We do not give any guarantees for compatibility of master with >> released or future versions and this should not hold us back from >> making any changes. >> >> We increase the version of master to 2.4.99 when we branch 2.4, >> like we normally do. As soon as installations of master are >> upgraded at least once, they would not get the released 2.4.0. > > Users running master might be in the habit of running "sudo port > selfupdate" regularly, as we recommend they do, which would update > their ports but not base, but only occasionally manually updating > their base source code and rebuilding base from it. After we update > master to be 2.4.99, users would have to know to update and rebuild > base manually before they selfupdate. We should communicate that to > users in advance so that they don't inadvertently selfupdate update > to 2.4.0. Or we should communicate how to use the trunk rsync > directory, if that's not already common knowledge. For installations of master, I would not recommend to run 'sudo port selfupdate', as there is no point in downloading sources for the latest release. Instead, use 'sudo port sync', which will only update your ports tree. This section in the guide needs rework anyway, so a future version should include a warning not to run selfupdate for installations from master: https://guide.macports.org/#installing.macports.subversion Rainer
