On 2013-8-8 02:34 , Mojca Miklavec wrote: > Hello, > > I'm wondering if it is possible to use a normal configure/make/make > install route for a subport which otherwise belongs to the Python > PortGroup. > > I would like to create a port which first installs the libraries via > the usual configuration process and then a bunch of subports > py2X-portname that install python support for those libraries. If I > add "PortGroup python 1.0" on top, then setup.py is expected even for > the part that should be installed the usual way.
Why would you want to use the portgroup if you're just going to override almost everything that it does? It's not hard to declare a bunch of subports called py2X-portname that just set configure.python or whatever the build systems needs. - Josh _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
