Clemens Lang cal at
Wed Jun 28 20:03:49 UTC 2017


On Wed, Jun 28, 2017 at 10:27:31AM +0200, Rainer Müller wrote:
> On 2017-06-28 00:28, Clemens Lang wrote:
> > How are those updated? Are we using the master manpages?
> I created a buildbot deploy job for that [1]. However, as we still
> lack a builder to run jobs on (also affects portindex, www, guide),
> the process is not fully automated yet.

OK. Should we eventually just create a Linux buildslave to do
non-OS-X-specific builds like this one?

> I hardcoded the relese-2.4 branch, to avoid publishing documentation
> for unreleased new features. It would be better if new releases would
> not require a new deploy of master.cfg. Not yet sure where to
> store/get the current release branch, though...

Use the livecheck URL that contains the latest MacPorts release, I
guess? Problem is you cannot know whether a tag is created first or the
macports_version file is modified first, so you'd probably have to build

Building once a day, or even once a week, and watching


for changes and a corresponding tag should be enough, though.


More information about the macports-dev mailing list