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

terminology page review: fix EasyBuild version, remove ancient paragraph #133

Merged
merged 5 commits into from
May 23, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
15 changes: 3 additions & 12 deletions docs/terminology.md
Original file line number Diff line number Diff line change
Expand Up @@ -37,9 +37,9 @@ See [Easyconfig files][easyconfig_files].

<!-- XXX - UPDATE BY VERSION FIXME -->

In EasyBuild version |version| the framework source code consists of about 19000 lines of code,
organized across about 125 Python modules in roughly a dozen Python package directories,
next to almost 7000 lines of code for tests. This provides some notion of the size of the
In EasyBuild version {{ easybuild.version }} the framework source code consists of about 31,500 lines of code,
organized across about 225 Python modules in roughly 20 Python package directories,
next to about 27,000 lines of code for tests. This provides some notion of the size of the
EasyBuild framework and the amount of supporting functionality it has to offer.


Expand Down Expand Up @@ -67,15 +67,6 @@ specification parameter (see [Easyblock specification][writing_easyconfigs_easyb
Since EasyBuild v2.0, an easyblock *must* be specified in case no matching easyblock is found based on the
software name (cfr. [Automagic fallback to ConfigureMake][depr_ConfigureMake_fallback_eb1]).

<!-- XXX - UPDATE BY VERSION FIXME -->

EasyBuild version 2.4.0 includes 154 software-specific easyblocks and 28 generic
easyblocks (see also [List of easyblocks][vsd_list_easyblocks]), providing support for automatically installing a wide range
of software packages. Examples range from fairly easy-to-build programs like gzip, other basic tools
like compilers, various MPI stacks and commonly used libraries, primarily for x86_64 architecture systems,
to large scientific software packages that are notorious for their involved and tedious install procedures, such as:
`CP2K`, `NWChem`, `OpenFOAM`, `QuantumESPRESSO`, `WRF`.


## Toolchains {: #toolchains }

Expand Down