| 1 | | I was more thinking of something like.... clang-3.4 declares a path like dependency, something like `path:lib/something.dylib:libcxx-bootstrap` so when it is first built it triggers the installation of libcxx-bootstrap. Then, later on, when clang5 etc. are built then keep the `port:libcxx` dep. Finally, `libcxx` would have to have some logic added to forcibly remove `libcxx-bootstrap` when it is built/installed, so effectively it replaces it. |
| | 1 | I was more thinking of something like.... clang-3.4 declares a path like dependency, something like `path:lib/something.dylib:libcxx-bootstrap` so when it is first built it triggers the installation of libcxx-bootstrap. Then, later on, when clang5 etc. are built they keep the `port:libcxx` dep. Finally, `libcxx` would have to have some logic added to forcibly remove `libcxx-bootstrap` when it is built/installed, so effectively it replaces it. |
