Re: missing pre-compiled packages

>> I wonder why some pre-compiled packages are missing: [...] If this >> is expected, where is it documented? > > Yes, it's expected that not all ports will have binaries available. > See . Thanks. > The automated license checking doesn't have

Re: missing pre-compiled packages

Chris Jones wrote: Binaries aren’t available if the licenses of the port, and its dependencies, do not allow it. To check if this is the case you should refer to the build logs which you can find from the ports site. E.g. https://ports.macports.org/port/git Then check the builds tab. Pick

Re: missing pre-compiled packages

Hi, Binaries aren’t available if the licenses of the port, and its dependencies, do not allow it. To check if this is the case you should refer to the build logs which you can find from the ports site. E.g. https://ports.macports.org/port/git Then check the builds tab. Pick one, and then

Re: missing pre-compiled packages

Werner LEMBERG wrote: I wonder why some pre-compiled packages are missing: * ccache – the directory `https://packages.macports.org/ccache/` is empty * git – the directory `https://packages.macports.org/git/`

missing pre-compiled packages

Folks, I wonder why some pre-compiled packages are missing: * ccache – the directory `https://packages.macports.org/ccache/` is empty * git – the directory `https://packages.macports.org/git/` doesn't exist at all If this is expected, where is it documented? Werner