From 15d32a7df7b2d4420bebd18b855f83606d872f30 Mon Sep 17 00:00:00 2001 From: Mohammad Akhlaghi Date: Mon, 21 Jan 2019 19:24:49 +0000 Subject: Metastore package now installed to allow keeping file meta-data The pipeline heavily depends on file meta data (and in particular the modification dates), for example the configuration-Makefiles within the pipeline are set as prerequisites to the rules of the pipeline. However, when Git checks out a branch, it doesn't preserve the meta-data of the files unique to that branch (for example program source files or configuration-Makefiles). As a result, the rules that depend on them will be re-done. This is especially troublesome in the scenario of this reproducible paper project because we commonly need to switch between branches (for example to import recent work in the pipeline into the projects). After some searching, I think the Metastore program is the best solution. Metastore is now built as part of the pipeline and through two Git hooks, it is called by Git to store the original meta-data of files into a binary file that is version controlled (and managed by Metastore). --- .file-metadata | Bin 0 -> 4492 bytes 1 file changed, 0 insertions(+), 0 deletions(-) create mode 100644 .file-metadata (limited to '.file-metadata') diff --git a/.file-metadata b/.file-metadata new file mode 100644 index 0000000..1eb83fa Binary files /dev/null and b/.file-metadata differ -- cgit v1.2.1