On Mon, Sep 14, 2009 at 11:02:08AM -0500, Ryan Schmidt wrote:
On Sep 14, 2009, at 11:00, Ryan Schmidt wrote:
On Sep 14, 2009, at 10:50, Jack Howarth wrote:
Actually one reason I asked the question was that
while trying to debug the problems I am seeing with
my test packaging of the molmol
On Sep 14, 2009, at 10:50, Jack Howarth wrote:
Actually one reason I asked the question was that
while trying to debug the problems I am seeing with
my test packaging of the molmol molecular modelling
program, I tried to build molmol against lesstif instead
of openmotif. In that case, the
On Mon, Sep 14, 2009 at 09:49:03AM -0500, Ryan Schmidt wrote:
We have the python_select script. Ideally ports would not require the
user to have selected a particular python, and would work with $
{prefix}/bin/python24 or whatever directly.
I believe the original idea was to avoid forcing
On Sep 14, 2009, at 09:37, Jack Howarth wrote:
Can someone explain the details of how the various
python packages in MacPorts co-exist? Most of the scientific
packages I maintained in fink (and will be porting to MacPorts)
use python/tcltk. I assume MacPorts doesn't really have the
same type
On 2009-09-14 18:21 , Jack Howarth wrote:
Yes, this is one thing I definitely miss from fink. Most packages providing
development libraries are either present as...
foobar headers
foobar-bin binaries
foobar-shlibs shared libraries
or
foobar-dev headers
foobar
