You can go either way with it, really. If there is a patch available to make it compile with clang, and upstream has accepted it for inclusion in future version X, then we could add it too, and remove it later once we update to version X. Or we could tell the port to use llvm-gcc-4.2 instead of clang, and remove that when we update to version X. We just have to remember to do either of those things when version X comes around. By using a patch, especially one already incorporated upstream, it's impossible not to remember, because the patch will fail and thus remind us. If we instead just set the port to use llvm-gcc-4.2 instead of clang, we might forget to remove that later. In either case, it would be a good idea to add a comment to the Portfile saying to remove the workaround when updating to version X.
_______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
