On Feb 15, 2013, at 4:10 AM, Jeremy Huddleston Sequoia <jerem...@macports.org> wrote:
> That is the entire point of this patch. macports-gcc-3.14 is perfectly valid > and should result in a dependency on gcc314. Of course the developer would > then see a lint error about an unknown port just like they would see if they > added 'depends_build port:gcc314' to the Portfile. Oh, I see. So the developer would just get the unknown port error instead of getting "Invalid value for configure.compiler: macports-gcc-3.14" during configure. Makes sense. No point in checking for the port if MacPorts does that already >.< vq _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
