Skip to content
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

Multiple tools for managing environment modules #39

Open
willfurnass opened this issue Jun 23, 2021 · 1 comment
Open

Multiple tools for managing environment modules #39

willfurnass opened this issue Jun 23, 2021 · 1 comment
Labels
enhancement New feature or request

Comments

@willfurnass
Copy link

willfurnass commented Jun 23, 2021

Lmod is installed explicitly on workers; environment-modules 4.x is pulled in on the mgmt node when gcc-toolset-9 is explicitly installed.

Is GCC 9 needed? If not, then is it better to just dnf group install "Development Tools" via Ansible on the mgmt node and in the Packer recipe and explicitly install and use one of Lmod or environment-modules everywhere?

@milliams milliams added the enhancement New feature or request label Jul 9, 2021
@milliams
Copy link
Member

milliams commented Jul 9, 2021

We started including GCC 9 when we were on CentOS 7 as a way of ensuring some modern tools. In CentOS we have decent base tooling so it's not required.

We want, in general, to keep the base package as simple as possible and encourage the use of self-compiled software or things like Singularity or podman for complex dependencies.

I agree that this needs cleaning up so thanks for raising the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants