Hi, > In my opinion increasing the version of the portgroup should be > reserved for (fundamentally) incompatible changes or when the syntax > changes. (For example when switching from qt4 to qt5 if the portgroup > would initially be just "qt". Or if the python PortGroup would start > working for software written in C++ with Python bindings.) I agree > that this kind of change in the cmake PortGroup is almost the > bordercase, but I feel that starting a new revision would introduce > way more work than benefits.
Incompatible changes would warrant an increase to the *major* portgroup version, so from 1.0 to 2.0 say. Increasing it from 1.0 to 1.1 seems to me pretty suited to this case, and thus I agree would have been a good idea. Chris
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
