On 2014-2-21 12:17 , Ryan Schmidt wrote:
>
> On Feb 20, 2014, at 09:44, Peter Danecek wrote:
>
>> On 20 Feb 2014, at 16:00, Jeremy Lavergne wrote:
>>
>>> packages.macports.org/PACKAGENAME/
>>
>> So looking up `http://packages.macports.org/py-obspy/` reveals that a binary
>> archives were produce
On Feb 20, 2014, at 09:44, Peter Danecek wrote:
> On 20 Feb 2014, at 16:00, Jeremy Lavergne wrote:
>
>> packages.macports.org/PACKAGENAME/
>
> So looking up `http://packages.macports.org/py-obspy/` reveals that a binary
> archives were produces some time ago. These are marked "noarch", which i
On 20 Feb 2014, at 16:00, Jeremy Lavergne wrote:
> packages.macports.org/PACKAGENAME/
So looking up `http://packages.macports.org/py-obspy/` reveals that a binary
archives were produces some time ago. These are marked "noarch", which is
probably wrong. There are compiled extensions. I do not
packages.macports.org/PACKAGENAME/
so, for pspp-devel for example, packages.macports.org/pspp-devel/
Perhaps it’s the license of the package that prevents the binaries? The logs
area available on the buildbot master for the mavericks post slave:
https://build.macports.org/buildslaves/apple-maver
Hi,
The first thing you should check is if the license in the Port file
allows for the binaries to be distributed ?
Chris
On 20/02/14 14:54, Peter Danecek wrote:
Hi all,
from a user report I realised that there is probably no binary archive
available for Maverick of one port I am maintain
Hi all,
from a user report I realised that there is probably no binary archive
available for Maverick of one port I am maintaining.
I am now, wondering if there is a way to obtain more information, e.g.
- Which binary archives exist and when these were produced?
- Are there problems with the bu
