PortGroup python 1.0 guidance
jmr at macports.org
Mon Jun 27 03:47:56 PDT 2016
On 2016-6-18 05:44 , Edward Maros wrote:
> I am working on a project that provides an interfaces to several
> scripting languages. One of these is Python. I have been working on
> using PortGroup python 1.0 to provide all the correct values for the
> python variant requested. The most notable is python.pkgd.
> The unfortunate side effect of using the python PortGroup for my
> project, is that I need to redefine all of my build, make, and install
> rules since my project isn't a pure python extension.
> Is there a way or could the python PortGroup be modified such that via a
> flag it could only generate the extended variables?
I think we should avoid scope creep in PortGroups if possible. It would
be better to make a different PortGroup for ports that don't build with
setup.py but want some of the paths and such. It could even share code
with the python PortGroup by sourcing a common file.
More information about the macports-dev