GIT modules
| GIT module | Version | Directory |
|---|---|---|
| ClioPatria | V3.1.1-59-g7b9a7a3 | /srv/ClioPatria |
| statistics | 283c62c | /srv/cliopatria/cpack/statistics |
| owl | b3b3e6c | /srv/cliopatria/cpack/owl |
| foaf | epoch-6-ge0db719 | /srv/cliopatria/cpack/foaf |
| isearch | cpackify-75-ga8000e5 | /srv/cliopatria/cpack/isearch |
| foaf_user | epoch-19-ge4cba43 | /srv/cliopatria/cpack/foaf_user |
| cpack_repository | epoch-169-gfd35698 | /srv/cliopatria/cpack/cpack_repository |
| swish | e487a27 | /srv/cliopatria/cpack/swish |
Server implementation language
SWI-Prolog version 10.1.18 (GIT version 10.1.18-30-gfe6698e26)
About GIT versions
Components are maintained using the GIT SCM
(Source Code Management) system. Instead of assigning versions by hand,
something which developers tend to forget, we leave this task to GIT. GIT's
versions are generated using the command git describe, which
describes a version with four components, separated with "-":
- The last contained tag. A tag is a label that the programmer gave to a version.
- The number of changes (commits) since the last tag. If there are no commits after the tag, this is omitted.
- If there are changes after the tag it also gives the GIT hash of the version. This number uniquely describes the version of the component.
- Finally, the text DIRTY is added if the actual files of the component do not match the files in the (local) repository. This means that one or more of the files has been edited locally.