From a0a51763a611faad22b7b2bc8ebbb5094b3377af Mon Sep 17 00:00:00 2001
From: Mohammad Akhlaghi <mohammad@akhlaghi.org>
Date: Tue, 8 Jun 2021 19:02:47 +0100
Subject: Minor edits and updated first-page Software Heritage ID

After going through Boud's corrections and edits in the previous commit, I
thought some minor clarifications would be necessary, and they are
implemented in this commit.

Also, in preparation for submission to the journal, the top-level software
heritage ID has been corrected to the latest commit on Software Heritage.
---
 tex/src/appendix-existing-solutions.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'tex/src/appendix-existing-solutions.tex')

diff --git a/tex/src/appendix-existing-solutions.tex b/tex/src/appendix-existing-solutions.tex
index 58a3518..578d6e9 100644
--- a/tex/src/appendix-existing-solutions.tex
+++ b/tex/src/appendix-existing-solutions.tex
@@ -437,7 +437,7 @@ It is possible to include the build instructions of the software used within the
 For the data, it is similarly not possible to extract which data server they came from.
 Hence two projects that each use a 1-terabyte dataset will need a full copy of that same 1-terabyte file in their bundle, making long-term preservation extremely expensive.
 Such files can be excluded from the bundle through modifications in the configuration file.
-However, this will add complexity if a higher-level script is written above ReproZip to make sure that the data and bundle are used together or to check the integrity of the data.
+However, this will add complexity: a higher-level script will be necessary with the ReproZip bundle, to make sure that the data and bundle are used together, or to check the integrity of the data (in case it may have changed).
 
 Finally, because it is only a snapshot of one moment in a project's history, preserving the connection between the ReproZip'd bundles of various points in a project's history is likely to be difficult (for example, when software or data are updated, or when analysis methods are modified).
 In other words, a ReproZip user will have to personally define an archival method to preserve the various black boxes of the project as it evolves, and tracking what has changed between the versions is not trivial.
-- 
cgit v1.2.1

