-
Notifications
You must be signed in to change notification settings - Fork 202
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Switching between naming schemes #1535
Comments
Changing this would be backwards compatible for everyone already using the new default and would also work seamlessly for other supported naming schemes (I think) but they would not be able to change naming scheme via the new script since only the new software would be in the correct installation path. |
@ocaisa: supporting using a fixed naming scheme for the installation directories makes a lot of sense indeed, I'm just not sure it's a good idea to make this the default Although EasyBuild itself or existing modules/installations won't mind, people may have made assumptions on the naming scheme used for the installation in other places, e.g. a script that crawls the installation directories (for whatever reason). So, your backward compatibility argument is not 100% correct. That said, we do have some other options if we do want to change the default to using a fixed naming scheme:
You mentioned you were going to look into implementing this yourself, thanks for that. Let's do that first, and then consider switching the default behaviour. I'm willing to consider it since i) it makes a lot of sense, ii) the impact is low, iii) we can poll up front via the ML whether this may impact people in one way or another. |
Thanks! |
One major hurdle when switching between naming schemes is that the default installation directory is dependent on the naming scheme. This is unnecessary since the module files themselves don't care where the installation is. Changing the default to a unique value, for example that used by easybuild_mns.py, would make switching naming schemes relatively trivial via a simple script:
--module-only
with new MNSI even think the default naming scheme tree should be created regardless of the naming scheme actually used just so you only need to indicate the new MNS when creating a new module tree.
The text was updated successfully, but these errors were encountered: