-
Notifications
You must be signed in to change notification settings - Fork 0
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
Enable custom autosave configuration #1
base: main
Are you sure you want to change the base?
Changes from 1 commit
60b37b4
9d1bcf7
a1199d9
30f8ffc
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2,6 +2,8 @@ TOP=.. | |
include $(TOP)/configure/CONFIG | ||
|
||
install: | ||
mkdir -p /usr/local/share/misc | ||
ln -s $(shell realpath $(TOP))/iocBoot/iocCamera/envPaths /usr/local/share/misc/ | ||
Comment on lines
+5
to
+6
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We could accept a Could you also add a comment to the commit message that There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Seems nice. Would
Sure. Will do. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Good enough. If you want to go further you can define |
||
ln -s $(shell realpath $(INSTALL_HOST_BIN))/Camera /usr/local/bin/ | ||
|
||
include $(CONFIG)/RULES_DIRS |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm wondering if
camera-envPaths
orenvPathsCamera
wouldn't be a better name... For namespacing reasons.(I prefer the second one)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To namespace it, I'd rather move it to a dedicated folder under
share
. Maybe/usr/local/share/ad-aravis{,-epics-ioc}/envPaths
. Other installed template scripts and configuration files could share the namespace this way.But then I fear we are losing the benefit of defining a (copy-and-paste) standard for different IOCs. Do we want to namespace to support different IOCs in the same container?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think things are strictly copy and paste now, since the binary has a specific name...
For most cases, I don't think so. But I feel like using a file in the same path for every container, which has different contents based on the container, can be a bit confusing; if the path is namespaced, then it's clear it's specific to this application.
Otherwise, for consistency, there should be a dynamic link to the
Camera
binary with a generic name (and we should document such a standard). I might be in favor of it if we go the whole way, but we can discuss more in person.