IMPORTANT: better names for to-publish dirs and portability fixesHEADmaneage

Summary: this commit only affects the analysis of your project in case you
used the 'tex-publish-dir' or 'data-publish-dir' directories. They need to
be renamed to 'figdir' and 'drdir' respectively.

Until now, the directories containing the to-be-published data were
described deep in the middle of 'initialize.mk' (away from the other shared
directories), they also had hard-to-use (long) names. Furthermore,
'README-hacking.md' that is the main documentation of Maneage had grown
organically, such that the checklists were scattered across the file and
some things were repeated or not classified clearly. Finally, some
portability issues were reported by Stergios Amarantidis and Diana Korotun.

With this commit, the to-be-published directories have been renamed to the
more simple names of 'figdir' and 'drdir' respectively and their definition
in 'initialize.mk' has come right under the rest of the top-level
directories (to be easily found). Furthermore, the 'README-hacking.md' has
been fully restructured to be easier to navigate and follow for a new
reader. Finally, the portability issues mentioned above have been
addressed:

 - Within the '--help' output of './project', the '--keep-going' option was
   listed under "Configure and Make options", while it is only relevant as
   a Make option. It was therefore moved under Make options.

 - We had not explicitly set the locale of Maneage; causing a crash on one
   of the newly tested computers (a macOS with a non-C locale) during the
   execution of 'prep-source.sh'. With this commit, all the top-level
   Makefiles and scripts of Maneage set 'LC_ALL' to 'C' to ensure the same
   locale on any system.

 - The 'download-multi-try.sh' script would crash when building basic
   software in the following scenario: the downloader was still from the
   host, but one of its linked libraries had already been installed in
   Maneage and conflicted with the host. A step has been added to catch
   such cases and remove the Maneage'd library when this was the problem.

 - On macOS, we discovered that 'pkg-config' and 'wget' need a Python
   installation, so the necessary conditions have been added.

 - The 'apptainer.sh' script did not allow passing the '--debug' or
   '--host-cc' options to the execution of './project' within the
   container.

 - Within 'configure.sh', we wrote the absolute path of the downloader to
   use in 'LOCAL.conf'. However, we install both downloaders and it is
   safer to use Maneage's own downloader when it has been installed. So the
   downloader name in 'LOCAL.conf' now only has the name (without its
   absolute path).

0 files changed, 0 insertions, 0 deletions