Hi there, I’m currently finalizing the Portfile for a new port, eero-devel, tied to the Eero language, an evolution of Obj-C in development (http://eerolanguage.org).
The Eero compiler is a extended version of Clang (it can also compile regular C, C++, Obj-C). At this point, there is no release, only a git repository, though the main developer, Andy Arvanitis, has agreed to tag the most meaningful revisions in order to ease downloading and dependency resolution. I have two choices: one is to use both the Eero tagged copies of llvm-trunk and clang-trunk, thereby making it a total autarkic port, but replicating llvm libraries; the other choice is to make it depend on llvm-3.2, but that would mean either asking Andy to place a tag each time the llvm-3.2 port is updated, or update llvm-3.2 Portfile each time Andy tags a new revision. What would be, according to you, the best option? Thanks a lot, have fun. Vincent _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-dev
