...
These defaults can be overruled for packages defined in the tags directory as follows:
• OPERATIONAL • DEPRECATED packages can explicitly be declared in the eups.cfg file defined at product level.
• EXPERIMENTAL packages can be declared by appending an 'E' to the package version (e.g. eeups-1.4.3+4E). Note that this is not necessary for trunk and branch packages.
In case OPERATIONAL packages are explicitly declared in the eups.cfg file, all the packages that are not declared OPERATIONAL or EXPERIMENTAL are considered DEPRECATED . In case no OPERATIONAL packages are declared in the eups.cfg file or in case no eups.cfg file is specified, all the packages that are not EXPERIMENTAL are considered OPERATIONAL.OPERATIONAL packages can be declared in the eups.cfg file by the following syntax:
| No Format |
|---|
OPERATIONALdeprecated = 1.2.3+10; 3.2.1+0; [5.2+3,6.3+2]; [6.5+0,6.6+3); [8.8+1,*), (*,1.2+1] |
Actually, for the ranges, a suitable ordering of the versions is adopted (the same ordering that you can see on the per product view in the eeups dashboard. Angular brackets indicate that boundary versions included, round brackets that boundary versions are excluded.
...