Imported recent updates in Maneage, conflicts fixed

Until now, Maneage had undergone some updates.

With this commit, those updates have been imported and the conflicts that
resulted were fixed. They were all cosmetic and had no effect on the
analysis. The most significant one was about the change in the format of
'INPUTS.conf'.

In the process, I also noticed that the IEEEtran LaTeX package is now
called 'ieeetran' (the 'tlmgr' of TeXLive 2022 was failing).

1 files changed, 23 insertions, 24 deletions

diff --git a/reproduce/analysis/make/prepare.mk b/reproduce/analysis/make/prepare.mk
index d0b61d9..ecb6842 100644
--- a/reproduce/analysis/make/prepare.mk
+++ b/reproduce/analysis/make/prepare.mk
@@ -1,6 +1,6 @@
-# Basic preparations, called by `./project prepare'.
+# Basic preparations, called by './project prepare'.
 #
-# Copyright (C) 2019-2021 Mohammad Akhlaghi <mohammad@akhlaghi.org>
+# Copyright (C) 2019-2022 Mohammad Akhlaghi <mohammad@akhlaghi.org>
 #
 # This Makefile is free software: you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -21,30 +21,29 @@
 
 # Final-target
 #
-# Without this file, `./project make' won't work.
+# Without this file, './project make' won't work.
 prepare-dep = $(subst prepare, ,$(makesrc))
 $(bsdir)/preparation-done.mk: \
                 $(foreach s, $(prepare-dep), $(mtexdir)/$(s).tex)
 
-        # If you need to add preparations define targets above to do the
-        # preparations, then set the value below to `yes'. Recall that just
-        # like `./project make', before loading this file, `./project
-        # prepare' loads loads `initialize.mk' and `download.mk', so you
-        # can safely assume everything that is defined there in the
-        # preparation phase also.
-        #
-        # TIP: the targets can actually be automatically generated
-        # Makefiles that are used by `./project make'. They can include
-        # variables, or automatically generated rules. Just make sure that
-        # those Makefiles aren't written in the source directory. Even
-        # though they are Makefiles, they are automatically built, so they
-        # don't belong in the source. `$(prepdir)' has been defined for
-        # this purpose (see `initialize.mk'), we recommend that you put all
-        # automatically generated Makefiles under this directory. In the
-        # `make' phase, `initialize.mk' will automatically load all the
-        # `*.mk' files. If you need to load your generated
-        # configuration-makefiles before automatically generated Makefiles
-        # containing rules, you can use some naming convension like
-        # `conf-*.mk' and `rule-*.mk', or you can put them in
-        # subdirectories.
+#	If you need to add preparations define targets above to do the
+#	preparations, then set the value below to 'yes'. Recall that just
+#	like './project make', before loading this file, './project
+#	prepare' loads loads 'initialize.mk' and 'download.mk', so you can
+#	safely assume everything that is defined there in the preparation
+#	phase also.
+#
+#	TIP: the targets can actually be automatically generated Makefiles
+#	that are used by './project make'. They can include variables, or
+#	automatically generated rules. Just make sure that those Makefiles
+#	aren't written in the source directory. Even though they are
+#	Makefiles, they are automatically built, so they don't belong in
+#	the source. '$(prepdir)' has been defined for this purpose (see
+#	'initialize.mk'), we recommend that you put all automatically
+#	generated Makefiles under this directory. In the 'make' phase,
+#	'initialize.mk' will automatically load all the '*.mk' files. If
+#	you need to load your generated configuration-makefiles before
+#	automatically generated Makefiles containing rules, you can use
+#	some naming convension like 'conf-*.mk' and 'rule-*.mk', or you can
+#	put them in subdirectories.
 	@echo "include-prepare-results = no" > $@