Skip to content

Commit

Permalink
Add note about checksums
Browse files Browse the repository at this point in the history
Co-authored-by: ocaisa <[email protected]>
  • Loading branch information
Flamefire and ocaisa authored Jan 9, 2025
1 parent 1d39c12 commit e69c6c1
Showing 1 changed file with 5 additions and 0 deletions.
5 changes: 5 additions & 0 deletions docs/writing-easyconfig-files.md
Original file line number Diff line number Diff line change
Expand Up @@ -953,6 +953,11 @@ So the process of updating an easyconfig to a newer toolchain version could look
1. Copy the easyconfig and change the toolchain version
1. Usually, especially when updating to the latest toolchain,
you should search for the most recent version of the software too and use that.
When you update the version, the checksum for the softwares sources will

Check failure on line 956 in docs/writing-easyconfig-files.md

View workflow job for this annotation

GitHub Actions / build

softwares ==> software
become incorrect and should be removed. You can automatically inject the
checksums for the new sources with `eb --inject-checksums <easyconfig>`
(see [checksums documentation](writing-easyconfig-files.md#common_easyconfig_param_sources_checksums)
for more details).
1. For each listed dependency find the easyconfig for the new toolchain version.
Here you need to take [toolchain hierarchy](common-toolchains.md#toolchains_diagram) into account.
I.e. a dependency of an easyconfig for the `foss` toolchain might use the `GCC` or `GCCcore` toolchain.
Expand Down

0 comments on commit e69c6c1

Please sign in to comment.