Easy access to external repositories.
David Strubbe
dstrubbe at macports.org
Mon Jun 1 14:00:47 PDT 2015
The buildslaves begin shortly after each commit. The delay, if any, is
probably a few minutes. Of course depending on how long it takes to build
the ports it may take a while to finish, and may have been busy building
other ports already when you commit.
When it cannot get the binary, that may be because of license issues,
because the build failed on the buildslave, or because you are using
non-default variants (and probably other reasons too).
On Mon, Jun 1, 2015 at 4:54 PM, Artur Szostak <aszostak at partner.eso.org>
wrote:
> Our software is all open source (GPL) so thats not the problem.
> What is the duty cycle or delay for the buildslaves to build these
> packages?
> I have seen a number of occasions where MacPorts cannot seem to find the
> binary for a Portfile from the default repository and builds the package
> locally.
>
> ------------------------------
> *From:* dstrubbe at gmail.com [dstrubbe at gmail.com] on behalf of David
> Strubbe [dstrubbe at macports.org]
> *Sent:* 01 June 2015 21:06
> *To:* Artur Szostak
> *Cc:* MacPorts Development
> *Subject:* Re: Easy access to external repositories.
>
> Provided the licenses for your software and its dependencies would make
> the binaries redistributable, the binaries will be built automatically for
> the default variants by the buildslaves (using various recent versions of
> OSX) after a commit of a Portfile to the MacPorts repository, and then
> those binaries will be available for users when they run 'port install'.
>
> David
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/macports-dev/attachments/20150601/fdc90218/attachment-0001.html>
More information about the macports-dev
mailing list