I've recently added FreeBSD ports for 3.5rc1 of LLVM and Clang as well as updated the 3.4 ports to 3.4.2 and was agressively reminded of a longstanding pet peeve with the release process. There is no release to release constancy of either tarball names or the names of the top level directory inside the tarballs. Some examples: clang-3.2.src.tar.gz llvm-3.2.src cfe-3.3.src.tar.gz cfe-3.3.src clang-3.4.src.tar.gz clang-3.4 cfe-3.4.2.src.tar.gz cfe-3.4.2.src cfe.src-3.5rc1.src.tar.gz cfe.src llvm-3.2.src.tar.gz llvm-3.2.src llvm-3.3.src.tar.gz llvm-3.3.src llvm-3.4.src.tar.gz llvm-3.4 llvm-3.4.2.src.tar.gz llvm-3.4.2.src llvm.src-3.5rc1.src.tar.gz llvm.src I propose the following changes: 0) What ever else we decide, write a script to do it and commit it to the repo so creating releases and snapshots is both easy and consistant. 1) Follow the common open source convention that <foo>.tar.gz extracts to <foo>. 1a) Consider an exception to the above for things like clang that can't build without llvm and have them extract to llvm-<version>/tools/<foo>. 2) Remove .src from file and directory names. After all, what else could it be? 3) Name the Clang tarball/directory clang not cfe. -- Brooks -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 181 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20140807/1e21df91/attachment.sig>