Difference between revisions of "Files/Script for checking EPM checksums"
(Created page with "This is a script for seeing whether files installed by an EPM from the Bazaar have been modified since installation. It only checks files under the core codebase and not unde...") |
|||
| Line 2: | Line 2: | ||
== Usage == | == Usage == | ||
| − | ./check_epm_checksums --eprints-path=/path/to/eprints/installation --ignore_list=/path/to/ignore/list/file | + | '''./check_epm_checksums''' --eprints-path=/path/to/eprints/installation --ignore_list=/path/to/ignore/list/file |
Latest revision as of 09:47, 22 November 2023
This is a script for seeing whether files installed by an EPM from the Bazaar have been modified since installation. It only checks files under the core codebase and not under the arechive's configuration (cfg) directory. As it is assumed that archive-level configuration files are likely to have been modified and should be managed under the archive's on version control (i.e. the repository owners' own Git, SVN, etc repository).
Usage
./check_epm_checksums --eprints-path=/path/to/eprints/installation --ignore_list=/path/to/ignore/list/file
