1. Generalities#
The rules for using the tools described here to manage the software configuration of Code_Aster aim to not overly constrain developers and to ensure that the changes made do not alter the proper functioning of the developments already made.
These goals will only be achieved:
if the developers are not trying to cheat with the system (experience has shown us that the rules already in place lead to such comfort that no one has tried to do),
because the code is managed centrally.
These rules are based mainly on three concepts:
extraction of the source, the system is reduced to its simplest expression since we simply warn the community that we want to modify a part of the given code,
Restitution, we check that there are no conflicts between the code rendered by a developer, the code developed by colleagues and the code already rendered in the reference version,
systematic passage of a set of reference tests before changes are taken into account.
The tools described in this document will be C-Shell scripts where possible and C programs for the rest.
For now, all of these tools should be available on the CRAY -C 98.
All tools must be able to be used in batch (qsub) and interactively.
Presentation note:
lowercase_mail_type_name:
represents a file CRAY from AGLA (in the general sense that is to say file or directory or command),
also represents an order or a concept related to CRAY and UNICOS,
represents a variable from a AGLA tool.