Alternative extensions

Obsoleto desde la versión 2.0: The .releng extension is no longer recommended and may be removed in a future release.

A default configuration file is typically a file named releng-tool.rt at the root of a project. Consider the following example of a project with a libfoo package with various stage scripts:

└── my-project/
    ├── package/
    │   └── libfoo/
    │       └── libfoo.rt
    │       └── libfoo-build.rt
    │       └── libfoo-install.rt
    └── releng-tool.rt

Developers who do not perfer the .rt extension may use alternatives, such as the .py extension or no extension at all. For example, the above example is equivalent to the structure:

└── my-project/
    ├── package/
    │   └── libfoo/
    │       └── libfoo
    │       └── libfoo-build
    │       └── libfoo-install
    └── releng-tool

Or the structure:

└── my-project/
    ├── package/
    │   └── libfoo/
    │       └── libfoo.py
    │       └── libfoo-build.py
    │       └── libfoo-install.py
    └── releng-tool.py

For a specific file to be loaded, releng-tool uses the following priority:

1. File without an extension

2. File with a .rt extension

3. File with a .releng extension (deprecated)

4. File with a .py extension

Only the first detected file will be loaded. For example, if a project has multiple releng-tool configuration files with different extensions:

└── my-project/
    ├── package/
    │   └── libfoo/
    │       └── ...
    ├── releng-tool.rt
    └── releng-tool.py

Only the releng-tool.rt configuration script will be used.