Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

adding more db and template files to the install directory #197

Merged
merged 1 commit into from
Nov 15, 2024

Conversation

hongran
Copy link
Contributor

@hongran hongran commented Nov 14, 2024

In APS we use many db and template files from the installed area to build our own data base. These files are needed by our build system.

@jerzyjamroz
Copy link
Contributor

@hongran , if you think it is useful, you can maintain the APS-specific (but generic enough) files within mrfioc2 (e.g. APSBeamStart or something would not go here - but its template, maybe yes).

@jerzyjamroz jerzyjamroz merged commit 5bd4c56 into epics-modules:master Nov 15, 2024
11 checks passed
@hongran
Copy link
Contributor Author

hongran commented Nov 15, 2024

@hongran , if you think it is useful, you can maintain the APS-specific (but generic enough) files within mrfioc2 (e.g. APSBeamStart or something would not go here - but its template, maybe yes).

@jerzyjamroz We don't need any APS-specific file in the mrfioc2 repository. Our site-specific files are just the evm-vme-300 and evr-vme-300 substitution files, with a different naming style. We store them in our IOC application repositories.

@jerzyjamroz
Copy link
Contributor

We don't need any APS-specific file in the mrfioc2 repository.

It is what I wrote and I referred to generic templates.

a different naming style

Just curiosity, what kind of naming cannot be done with the existing substitutions?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants