You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
or simply a non-executable in installed within /bin/ such as tesseract.conf.
These options don't feel like good practices. Should these dependent files be written to a different directory (not /bin) and called with a relative path from the associated scripts?
The text was updated successfully, but these errors were encountered:
It looks like some of these (such as the embedded xsl) could be externalized and then installed into an mm specific config directory using 'etc.install' option in the mm homebrew formula. This might still result in an absolute path however.
Testing showed that the previous method works, except that it might complicate future changes. Reinstalling doesn't write over the old file, it just creates a new file with .default appended to it (e.g. makemets.xml.default). Any scripts would have to take this into account otherwise updates to the file dependencies would have to be manually applied to existing files.
Currently non-bash file dependencies are either written into the bash script and echoed out into a temporary files, such as the xsl embedded within
mm/makemets
Lines 5 to 121 in 90e07c5
/bin/
such as tesseract.conf.These options don't feel like good practices. Should these dependent files be written to a different directory (not
/bin
) and called with a relative path from the associated scripts?The text was updated successfully, but these errors were encountered: