On Oct 1, 2014, at 3:08 PM, Frank Schima <m...@macports.org> wrote: > On Oct 1, 2014, at 12:26 PM, Sean Farley <s...@macports.org> wrote: > >> We really should be consistent then. I personally don't care what the >> new name is but we should either have clangX.Y / gccX.Y or clangXY / >> gccXY. > > I say we use gccX.Y. Just renaming gcc ports (for now) won’t be too hard.
Except that base automatically adds dependencies on `gccXY` depending on configure.compiler, so renaming them requires some sort of migration strategy. Either we wait until a new MacPorts release, or we jury-rig some sort of stub-port thing. vq _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
