On Mar 3, 2009, at 11:28, mm...@macports.org wrote:
Revision: 47678
http://trac.macports.org/changeset/47678
Author: mm...@macports.org
Date: 2009-03-03 09:28:49 -0800 (Tue, 03 Mar 2009)
Log Message:
---
build hdf5-18 with dynamic libs instead of static libs
Doesn't
On Mar 3, 2009, at 22:43, t...@macports.org wrote:
use sw_vers -productVersion (breaks jaguar compatibility)
Please change this back to the way it was. I deliberately used a call
that would work on all versions of Mac OS X that have ever existed so
that users who attempt an install on an
On Wed, Mar 4, 2009 at 12:46 AM, Ryan Schmidt ryandes...@macports.org wrote:
On Mar 3, 2009, at 22:43, t...@macports.org wrote:
use sw_vers -productVersion (breaks jaguar compatibility)
Please change this back to the way it was. I deliberately used a call that
would work on all versions of
On Mar 4, 2009, at 2:41 AM, Ryan Schmidt wrote:
On Mar 3, 2009, at 11:28, mm...@macports.org wrote:
Revision: 47678
http://trac.macports.org/changeset/47678
Author: mm...@macports.org
Date: 2009-03-03 09:28:49 -0800 (Tue, 03 Mar 2009)
Log Message:
---
build hdf5-18
What's the policy for updating ports that build in parallel to use
parallel_build yes?
Should tickets be made for ones that are maintained or just slip that
change in (given that you actually can build them in parallel)?
smime.p7s
Description: S/MIME cryptographic signature
Jeremy Lavergne wrote:
What's the policy for updating ports that build in parallel to use
parallel_build yes?
Should tickets be made for ones that are maintained or just slip that
change in (given that you actually can build them in parallel)?
Go ahead if it's nomaintainer or
