-
Notifications
You must be signed in to change notification settings - Fork 24
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
add page on beta releases & release candidates for EasyBuild v5.0 #284
base: main
Are you sure you want to change the base?
Conversation
- the **default settting of some configuration options has changed**: | ||
- **RPATH linking** is used by default (can be disabled with `--disable-rpath`); | ||
- **trace output** is enabled by default (can be disabled with `--disable-trace`); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
might be worth mentioning we now also enable --module-extensions
and --module-depends-on
by default as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Already done for --module-depends-on
, but will also cover --module-extensions
|
||
It can be used for testing and providing feedback (reporting bugs or unexpected behaviour, etc.). | ||
|
||
Additional changes will be made for the release of EasyBuild v5.0.0 however, [see below][beta1_planned_changes]. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Additional changes will be made for the release of EasyBuild v5.0.0 however, [see below][beta1_planned_changes]. | |
Additional changes can still be made before the release of EasyBuild v5.0.0, [see below][beta1_planned_changes]. |
|
||
### Highlighted changes | ||
|
||
EasyBuild v5.0.0 will include some significant changes compared to EasyBuild v4.x that you should be aware of, including: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
EasyBuild v5.0.0 will include some significant changes compared to EasyBuild v4.x that you should be aware of, including: | |
EasyBuild v5.0.0 will include some significant changes compared to EasyBuild v4.x. Some of those changes are internal improvements and will be invisible to most users. But many others need special attention as they incorporate new features, changes of behavior or deprecations that can impact your workflows: |
- the `use_pip` and `sanity_pip_check` custom easyconfig parameters used by the `PythonPackage` and `PythonBundle` easyblocks are enabled by default; | ||
- **some functionality has been deprecated**, including the use of the `run_cmd` and `run_cmd_qa` functions (`run_shell_cmd` should be used instead); | ||
- easyconfigs using an old [unsupported toolchain](../policies/toolchains.md) have been moved to the [easyconfigs archive](https://github.com/easybuilders/easybuild-easyconfigs-archive); | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe also mention:
- EB_PYTHON_PREFIX
- reproducible tarballs from git repos
- granular exit codes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I consider granular exit code too much of a detail here.
What should I mention exactly on EB_PYTHON_PREFIX
, is that really relevant here?
This is by no means meant to be a complete overview.
I will include an extra bullet on the reproducible tarballs though
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The important bit about EB_PYTHON_PREFIX
is that Python packages provided through EasyBuild can now be overwritten by user installations with venvs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That seems difficult to explain in a one-liner to me, we'll need a dedicated section in the documentation on that?
… v5.0.0beta1 release
No description provided.