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

Update site/packages.yaml and site/modules.yaml #1322

Open
wants to merge 1 commit into
base: release/1.8.0
Choose a base branch
from

Conversation

RatkoVasic-NOAA
Copy link
Collaborator

Summary

Latest changes in site/packages.yaml and site/modules.yaml config files regarding ecFlow and QT. Removed exclude for creating ecflow modulefile, added path for qt and removed ecflow from package list.

Testing

Installed already on Tier1 machines

Issue(s) addressed

Working on #1278

Checklist

  • This PR addresses one issue/problem/enhancement, or has a very good reason for not doing so.
  • These changes have been tested on the affected systems and applications.
  • All dependency PRs/issues have been resolved and this PR can be merged.

Copy link
Collaborator

@climbfuji climbfuji left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

qt:
externals:
- spec: [email protected]
prefix: /scratch1/NCEPDEV/nems/role.epic/installs/qt-5.12.6/qtbase
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is the plan to eventually install the external qt's under contrib space on various systems?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know about plans. I remember is was PITA to install it, you had to login to do that (used Dom's account). But lately I found it was easy to install from github, something like 'research' version.
Also, some systems have already installations of qt, but I couldn't use it because it was built with different gcc version and we couldn't link it with ecflow under spack-stack.

@climbfuji
Copy link
Collaborator

I am considering retagging the release after this PR goes in, and then we'll also need to cherry-pick this particular PR (which will be merged as a squashed merge) for develop.

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

Successfully merging this pull request may close these issues.

3 participants