[110106] trunk/dports/math/octave-devel/Portfile

[Michael Dickens]

On Mon, Aug 26, 2013, at 04:15 AM, jeremyhu at macports.org wrote:
> Revision 110106
> Author: jeremyhu at macports.org
> Date: 2013-08-26 01:15:41 -0700 (Mon, 26 Aug 2013)
> Log Message: octave-devel: Use fortran recipe like octave

I just updated my local SVN repository of MacPorts, then went and built
"port" fresh and installed it so I know it is the latest and greatest
("port version" verifies this, since I use my own local versioning).

When I do "port variants octave-devel" I see the variants but no
descriptions for the +gcc4X ones, nor conflicts or so forth. Further, I
can pick multiple of the +gcc4X variants; the highest numbered "X" wins
out -- but, only one +gcc4X variant should be allowed at a time and port
should handle the conflicts. These results say to me that this commit,
while well intentioned, has flaws.

Although I appreciate all of the changes going on behind the scenes to
get libgcc, libstdc++, and so forth standardized across compilers, I
wish folks would verify changes like this one before committing. I, as
the primary maintainer, now get to go back and undo/redo those changes,
which were not even -my- changes, to get things working again properly.

Would this have happened if I were the sole maintainer, no
"openmaintainer" along with me? That would help me feel better about the
way MacPorts commits work. - MLD