You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should set up an easybuild-experimental repository for hosting auto-generated easyconfig files, and potentially also easyblocks.
These could be generated from other build tools, e.g., pkgsrc, ports, portage, ...
This repository could then serve as a starting point for adding support for software that's already supported somewhere else. The auto-generated easyconfigs/blocks would still need human verification, e.g. adding sanity checks and validation installation correctness, before they are pushed to the main EasyBuild repository.
The text was updated successfully, but these errors were encountered:
Your proposal with alpha/beta/release subdirectories and additional structure for sources looks great to me.
Once you've set it up like you propose, can you write up a wiki page that we can thrown on the EasyBuild main wiki?
We needs this to be documented if we ever want people to use it.
It should mention what the purpose is of this repository, how the easyconfigs that are available there are generated, and how they should be used.
We should set up an
easybuild-experimental
repository for hosting auto-generated easyconfig files, and potentially also easyblocks.These could be generated from other build tools, e.g., pkgsrc, ports, portage, ...
This repository could then serve as a starting point for adding support for software that's already supported somewhere else. The auto-generated easyconfigs/blocks would still need human verification, e.g. adding sanity checks and validation installation correctness, before they are pushed to the main EasyBuild repository.
The text was updated successfully, but these errors were encountered: