4f0a8fce52
These 7 hooks were not used. - Six of them related to install phases were unused after `spack` `monitor` was removed, and the code seems to have bit rotten as there were reports they were not (always?) triggered when they should. - The post environment one was made redundant after spack install for environment started following the common code path for generating module files in #42147. It should not be a breaking change to remove, since users cannot define hooks in extensions, they would have to fork Spack. If we ever _were_ to make those hooks extendable outside of core Spack, it would also be better to start with fewer rather than more, cause everything you expose gets relied upon... Removing those also allows us to rethink what hooks we really need, and in particular it seems like we need a hook that runs post install also when the spec is inserted into the database. |
||
|---|---|---|
| .. | ||
| spack | ||