-
Notifications
You must be signed in to change notification settings - Fork 2
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
RHEL8 Workstation Installation requirements #13
Comments
I'll make sure these are in the list. Can you explain what you mean by the python3 workflow? Is it the one I currently understand which is "release from the devcontainer, run natively" or something else? |
Python 3 pipenv and python3 itself work natively on RHEL8 workstation with those 2 libraries. I guess saying the workflow works was incorrect since I'm sure dls-release will not work without the container. But python3 apps will run - even e.g. dls-pmac-control.py |
@aawdls Do you think we should put VSCode on this list? |
Yes. There are the installations in /dls_sw/apps maintained by someone (unknown to me), but we need to decide whether we want to continue using these or a system package. |
I think it is more appropriate to leave this kind of thing to the user. It is straightforward to install system packages. It might also make sense to assign someone (formally) to regularly update the vscode module, as it is a tool used by many people at Diamond. I think we are trying to move away from standard installs of tools etc, and allow people to opt-in to them. This is in that category. Standard installs should be reserved for basic functionality, in my view. |
@MJGaughran re installing system packages. Some of us with pcXXXX machines can do that but those with wsXXXX cannot and the distribution seems random. For your policy to work we need to make sure people get yum rights. Or am I misunderstanding you? |
@aawdls
We need a couple of things to add to the list for RHEL 8 installation:
The libraries make dls-python3 work on RHEL8 and the python3 workflow should then be good to go.
The text was updated successfully, but these errors were encountered: