Hello,
I realized today that after a recent patch the +universal variant of
AquaTerm doesn't install properly any more (framework ends up in
/Library/Framework and app installs to a completely weird location). I
don't know why exactly. The following workaround (under post-patch
section) hardcodes
There are some ports that cannot build on specific os.major; is there a way we
can have an accepted error message that the buildbot will not report as an
error?
Can we make it so `return -code error "unsupported OS X version"` is not an
error?
___
ma
On 2012-8-27 01:06 , Lawrence Velázquez wrote:
> On Aug 26, 2012, at 10:16 a.m., Ben Smith wrote:
>
>> Looking at your reference:
>>
>>
>>> guide.macports.org/chunked/reference.portgroup.html#reference.portgroup.python.sugar
>>
>>
>> Am I reading this right? The setup.py file is called multiple ti
On Aug 26, 2012, at 10:16 a.m., Ben Smith wrote:
> Looking at your reference:
>
>
> > guide.macports.org/chunked/reference.portgroup.html#reference.portgroup.python.sugar
>
>
> Am I reading this right? The setup.py file is called multiple times in
> multiple stages, but ISN'T passed the desti
Looking at your reference:
>
guide.macports.org/chunked/reference.portgroup.html#reference.portgroup.python.sugar
Am I reading this right? The setup.py file is called multiple times in
multiple stages, but ISN'T passed the destination of the files? How does
that work, why would you call the sa
On 2012-8-26 08:22 , Ben Smith wrote:
> I have two python apps (I'm saying apps instead of scripts because
> each contains multiple files -- I'm not sure if that's going to cause
> a problem yet either), that run on the command line: HeapCL and
> TorchCL. The concept/implementation is very close t
