Conversation
|
Hi @johnwparent! I noticed that the following package(s) don't yet have maintainers:
Are you interested in adopting any of these package(s)? If so, simply add the following to the package class: maintainers = ["johnwparent"]If not, could you contact the developers of this package and see if they are interested? You can quickly see who has worked on a package with $ spack blame lz4Thank you for your help! Please don't add maintainers without their consent. You don't have to be a Spack expert or package developer in order to be a "maintainer," it just gives us a list of users willing to review PRs or debug issues relating to this package. A package can have multiple maintainers; just add a list of GitHub handles of anyone who wants to volunteer. |
| @run_after("install") | ||
| def darwin_fix(self): | ||
| if sys.platform == "darwin": | ||
| fix_darwin_install_name(self.prefix.lib) |
There was a problem hiding this comment.
Once you add builders, these methods should be on the builders (otherwise they are not taken into consideration). I'll check how easy it is to add an audit for stuff like this.
Bug was introduced in spack#35101
lz4 - add CMake build system
lz4 build in serial on Windows - otherwise there is a transient build error caused by Ninja over parallelizing the build and dependent targets being built out of order due to the structure of the lz4 CMake system.
lz4 - multi buildsystem refactor
Part of #34938