python install anomalies - tcl code to set paths

Darren Weber dweber at macports.org
Fri May 22 16:59:28 PDT 2009


On Fri, May 22, 2009 at 3:58 PM, Rainer Müller <raimue at macports.org> wrote:

> On 2009-05-22 21:07, Darren Weber wrote:
> > The following tcl code should work for python 2.4, 2.5, and 2.6 (as of
> > May 2009).  The nice thing about this tcl code is that a port can use it
> > to set a python dependency for configuration that will be specific to a
> > python version.  This proc can be called from within variants to set or
> > reset a python dependency easily (e.g., say you want more than one
> > python variant to depend on a specific python install).
>
> The pythonXX port groups already define some variables. Would it make
> sense to have your proposed code in another port group? At least we
> should stick to the same variable names.
>
> Rainer
>


It's good to raise this point.  It's occurred to me that the python port
group might define a lot of this already.  I've not done any research on
this to consider whether to integrate this tcl proc into the python port
group or to adopt the variable names of the port group in this tcl proc.

The motivation for this was to provide a small procedural abstraction,
within a Portfile, to make it easier to define multiple pyXY variants.  It's
been useful in vtk-devel and InsightToolkit (revision 1 to be committed
soon), where it should be possible to build with one of several possible
python installations.  The proc abstraction in the Portfile avoids any
concern about using the python port group.  Given that vtk-devel and
InsightToolkit are not specifically python ports, I didn't want to
complicate them with the addition of the python port group (which was partly
a lazy decision based on ignorance).

Anyhow, this post to the dev list might help others with similar problems.
Perhaps someone familiar with the purpose and intent of the python port
group can take a look at this tcl proc to see if it might add anything
useful to the port group.

Best, Darren
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-dev/attachments/20090522/ff64bbfe/attachment.html>


More information about the macports-dev mailing list