From 621289494d23d3ac0b383d63371205cb826ccb8c Mon Sep 17 00:00:00 2001 From: Mohammad Akhlaghi Date: Sat, 28 Sep 2019 21:46:18 +0100 Subject: Main project script sets executable flags at configure time Until now, when the project's source was downloaded from something like arXiv, in `README.md', we were instructing them to set the executable flags of all the files that need it. But except for `./project', the reader shouldn't have to worry about the project internals! Once its executable, `./project' can easily fix the executable flags of all the files that need it automatically. With this commit, in `README.md', we just instruct the reader to set the executable flag of `./project' and any other file that needs an executable flag is given one at the start of the set of commands for `./project configure'. In customized projects, if an author needs executable flags on any other files, they can easily add it there without involving the user. --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'README.md') diff --git a/README.md b/README.md index 3dd2757..f0f6acc 100644 --- a/README.md +++ b/README.md @@ -112,11 +112,11 @@ this source from arXiv, some minor extra steps are necessary: 2. arXiv removes the executable flag from the files (for its own security). So before following the standard procedure of projects - described in the sections above, its necessary to make the necessary - script files executable with the command below: + described in the sections above, its necessary to set the executable + flag of the main project management file with this command: ```shell - $ chmod +x project reproduce/software/bash/* reproduce/analysis/bash/* + $ chmod +x project ``` 3. Remove extra files. In order to make sure arXiv can build the paper -- cgit v1.2.1