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
Search for runtime files in shared directory, to support system-wide installation #68
Conversation
@taviso what do you think about this approach? The location for the default config file can admittedly be nicer, e.g. |
4c91f22
to
4f1abaf
Compare
Check directories relative to the directory executable is run from. If runtime files dir is not found under ${exedir}/root/lotus, try searching in ${exedir}/../share/lotus This should help support system-wide installation and packaging.
Thinking about this further, another approach could be:
Then either:
or:
|
Discussion related to #20 |
Sorry for the slow response - I was focused on the keymap issue. This looks good to me, I rolled back the extract script temporarily because of bug reports, as soon as that returns I think this is good to merge. |
No rush. I can create a new branch with the fixed extract file and with the unified filesystem approach described above:
|
@taviso Created a new PR based on current Some files have been moved around (most notably binary is now built as |
Thank you, closing as #70 has now been merged instead. |
Check directories relative to the directory the executable is run from.
If runtime files dir is not found under
${exedir}/root/lotus
, try searching in${exedir}/../share/lotus
.This should help support system-wide installation and packaging.
Related to issue #66