On Fri, May 1, 2015 at 3:43 AM, Ryan Schmidt wrote: > >> And what should the default value be? C++11? C11? > > I think we should probably move toward portgroups where the default is not to > do anything, and some directive has to be used to activate the portgroup's > behavior.
Indeed. I often wish I was able to use the Python PortGroup to be able to recall some complex variables from the PortGroup for C++ projects with some Python bindings. But the PortGroup itself changes so much that there's no way to use it and also no way to "recover"/"revert" back to the default behaviour. So we end up hardcoding Python variables in regular ports, while that could/should be handled by the PortGroup. (The wxWidgets PortGroup doesn't do anything at by itself all for example, exactly for the reasons you mention: it might only be used in variants etc.) Including the PortGroup first and setting the required standard like C++11 or C++14 at some later point sounds reasonable to me. Mojca _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
