I managed to package epics base 3.15.6 and some other support modules as RPM package to be included in our local CentOS repo. Recently we thought of creating a global repo to be shared
with the community, but the big problem we faced is the choice epics base version.
Anything that depends on EPICS base must have its EPICS_BASE defined in the configure/RELEASE file, and since there are more than one major version of EPICS, some might try base 3.14,
3.15 or 3.16 or even 7. In order for the RPM spec file to work properly, EPICS_BASE must be hardcoded in configure/RELEASE. So the question is, does it make since to create separate repo for each base version and each repo contains all support modules built
against the corresponding base version? What we think of right now is 4 repos: base 3.14, base 3.15, base 3.16 and base 7. What do you think of this approach?
Tel: (+962-5) 3511348 , ext. 265
Fax: (+962-5) 3511423