diff options
| author | Mohammad Akhlaghi <mohammad@akhlaghi.org> | 2020-09-24 02:15:40 +0100 |
|---|---|---|
| committer | Mohammad Akhlaghi <mohammad@akhlaghi.org> | 2020-09-24 02:15:40 +0100 |
| commit | ee8c6be24166c16df9cd7fb1912503e25bdfde85 (patch) | |
| tree | 06f7fe4b75a48654174bb699149a204660a09b18 /README-hacking.md | |
| parent | 0c882a44e43a95761ffecdeebb57f2709e6f96e5 (diff) | |
Gnuastro's analysis configuration files removed
Until now, the core Maneage branch included some configuration files for
Gnuastro's programs. This was actually a remnant of the distant past when
Maneage didn't actually build its own software and we had to rely on the
host's software versions. This file contained the configuration files
specific to Gnuastro for this project and also had a feature to avoid
checking the host's own configuration files.
However, we now build all our software ourselves with fixed configuration
files (for the version that is being installed and its version is
stored). So those extra configuration files were just extra and caused
confusion and problems in some scenarios. With this commit, those extra
files are now removed.
Also, two small issues are also addressed in parallel with this commit:
- When running './project make clean', the 'hardware-parameters.tex' macro
file (which is created by './project configure' is not deleted.
- The project title is now written into the default output's PDF's
properties (through 'hypersetup' in 'tex/src/preamble-header.tex')
through the LaTeX macro.
All these issues were found and fixed with the help of Samane Raji.
Diffstat (limited to 'README-hacking.md')
| -rw-r--r-- | README-hacking.md | 8 |
1 files changed, 3 insertions, 5 deletions
diff --git a/README-hacking.md b/README-hacking.md index a598373..afa9a1d 100644 --- a/README-hacking.md +++ b/README-hacking.md @@ -1254,11 +1254,9 @@ for the benefit of others. - *Configuration files*: If your research uses special programs as part of the processing, put all their configuration files in a devoted directory (with the program's name) within - `reproduce/software/config`. Similar to the - `reproduce/software/config/gnuastro` directory (which is put in - Maneage as a demo in case you use GNU Astronomy Utilities). It is - much cleaner and readable (thus less buggy) to avoid mixing the - configuration files, even if there is no technical necessity. + `reproduce/software/config`. It is much cleaner and readable (thus + less buggy) to avoid mixing the configuration files, even if there is + no technical necessity. - **Contents**: It is good practice to follow the following |