The following features should be highlighted:
* the **definition** of the application content: which products (prerequisites, codes, modules) are necessary and which versions are required
- * the **configuration** of the application : how to get the source of products, how to compile them, which options to use, etc. The configuration can be conditionnaly overwritten, this feature allows application developers taking into account platform specifics.
+ * the **configuration** of the application : how to get the source of products, how to compile them, which options to use, etc. The configuration can be conditionally overwritten, this feature allows application developers taking into account platform specifics.
* the **preparation** of the complete software: all the required sources with correct versions are retrieved from git/svn/cvs repositories, or from already prepared tarballs.
* management of **patches** if some are required to compile on specific platforms (portage)
* management of the **environment** to set up at compile time and at runtime
* **overwriting** the configuration in command line: it allows users setting easily their own preferences or options
SAT uses **python**, and many of its strength come from its power and straightforwardness. It is compatible with both python2 and python3 versions.
-SAT is a Command Line Interface (CLI_) based on python langage. It is a suite of commands, which are detailed later in this documentation.
+SAT is a Command Line Interface (CLI_) based on python language. It is a suite of commands, which are detailed later in this documentation.
These commands are used to perform the operations on the application. SAT enables command completion by sourcing the provided complete_sat.sh script.
Like similar tool, SAT doesn't like modified environments, as this can cause conflicts while compiling products or using applications. It is recommended that SAT users run with a **clean environment**, especially for PATH, LD_LIBRARY_PATH and PYTHONPATH. ~/.bashrc file should be as thin as possible!
.. toctree::
:maxdepth: 1
+ Release Notes 5.8.0 <release_notes/release_notes_5.8.0>
Release Notes 5.7.0 <release_notes/release_notes_5.7.0>
Release Notes 5.6.0 <release_notes/release_notes_5.6.0>
Release Notes 5.5.0 <release_notes/release_notes_5.5.0>
