Add important note about mkiocccentry execution

It is highly recommended that you run the tool from either the repo
directory itself (making sure you have the most up to date version of
course) or make sure you have installed it (also making sure you have
the most recent version). Not doing this will cause issues with checks
and in the case of out of date versions the submission would be rejected
due to violating rule 17. One can specify the options to mkiocccentry
for the tools required but if you forget or don't have the most up to
date version you will very likely run into problems.

faq.html

@@ -697,6 +697,16 @@ <h4 id="q-0.1.4-how-do-i-use-mkiocccentry">Q 0.1.4: How do I use mkiocccentry?</
 username, which is <strong>in the form of a UUID</strong>, and submission number; see the
 <a href="next/rules.html">rules</a> for more details on this, and in particular <a href="next/rules.html#rule17">Rule
 17</a>.</p>
+<p><strong>IMPORTANT NOTE</strong>: if you run the program outside the repo directory
+(specifying the absolute or relative path to the tool) and you have not
+installed the tools then you will have to specify the options for the tools that
+are required like <code>chkentry(1)</code>, <code>txzchk(1)</code> and <code>fnamchk(1)</code>. But even if you
+have installed them but some tools are out of date (in the install path) it will
+cause problems. Additionally, if you do not have the most recent version when
+submitting a tarball it will be rejected for not having the right versions of
+the tools. This is why you <strong>MUST</strong> make sure you have the most recent version
+of all the tools and you either run it from the repo directory itself OR you
+install them (<code>make install</code> as via <code>sudo</code> or as root).</p>
 <p>If the <strong><em>subdirectory</em> in the <em>work directory</em></strong> (based on your submit ID and
 slot number) already exists, you will have to
 move it, remove it or otherwise specify a different work directory (<strong>NOT</strong> the

faq.md

@@ -319,6 +319,17 @@ username, which is **in the form of a UUID**, and submission number; see the
 [rules](next/rules.html) for more details on this, and in particular [Rule
 17](next/rules.html#rule17).
 
+**IMPORTANT NOTE**: if you run the program outside the repo directory
+(specifying the absolute or relative path to the tool) and you have not
+installed the tools then you will have to specify the options for the tools that
+are required like `chkentry(1)`, `txzchk(1)` and `fnamchk(1)`. But even if you
+have installed them but some tools are out of date (in the install path) it will
+cause problems. Additionally, if you do not have the most recent version when
+submitting a tarball it will be rejected for not having the right versions of
+the tools. This is why you **MUST** make sure you have the most recent version
+of all the tools and you either run it from the repo directory itself OR you
+install them (`make install` as via `sudo` or as root).
+
 If the **_subdirectory_ in the _work directory_** (based on your submit ID and
 slot number) already exists, you will have to
 move it, remove it or otherwise specify a different work directory (**NOT** the

next/guidelines.html

@@ -609,6 +609,18 @@ <h1 id="whats-new-this-ioccc">WHAT’S NEW THIS IOCCC</h1>
 before this option will work a second time, just like in normal mode.
 </p>
 <p class="leftbar">
+<strong>IMPORTANT NOTE</strong>: if you run the program outside the repo directory
+(specifying the absolute or relative path to the tool) and you have not
+installed the tools then you will have to specify the options for the tools that
+are required like <code>chkentry(1)</code>, <code>txzchk(1)</code> and <code>fnamchk(1)</code>. But even if you
+have installed them but some tools are out of date (in the install path) it will
+cause problems. Additionally, if you do not have the most recent version when
+submitting a tarball it will be rejected for not having the right versions of
+the tools. This is why you <strong>MUST</strong> make sure you have the most recent
+version of all the tools and you either run it from the repo directory itself OR
+you install them (<code>make install</code> as via <code>sudo</code> or as root).
+</p>
+<p class="leftbar">
 <a href="rules.html#rule17">Rule 17</a> has been <strong>significantly modified</strong>
 to account for the new <a href="https://github.com/ioccc-src/mkiocccentry">mkiocccentry repo</a> tools.
 Thus, you are <strong>STRONGLY</strong> advised to use the <code>mkiocccentry(1)</code> tool

next/guidelines.md

@@ -233,6 +233,19 @@ that if the directory exists already, you will have to remove it or move it
 before this option will work a second time, just like in normal mode.
 </p>
 
+<p class="leftbar">
+**IMPORTANT NOTE**: if you run the program outside the repo directory
+(specifying the absolute or relative path to the tool) and you have not
+installed the tools then you will have to specify the options for the tools that
+are required like `chkentry(1)`, `txzchk(1)` and `fnamchk(1)`. But even if you
+have installed them but some tools are out of date (in the install path) it will
+cause problems. Additionally, if you do not have the most recent version when
+submitting a tarball it will be rejected for not having the right versions of
+the tools. This is why you **MUST** make sure you have the most recent
+version of all the tools and you either run it from the repo directory itself OR
+you install them (`make install` as via `sudo` or as root).
+</p>
+
 <p class="leftbar">
 [Rule 17](rules.html#rule17) has been **significantly modified**
 to account for the new [mkiocccentry repo](https://github.com/ioccc-src/mkiocccentry) tools.

quick-start.html

@@ -540,6 +540,16 @@ <h4 id="run-the-mkiocccentry-tool-to-form-your-submission-tarball">6. Run the mk
 submission’s directory. See the
 FAQ on “<strong><a href="https://github.com/ioccc-src/mkiocccentry/blob/master/FAQ.md#install">installing mkiocccentry</a></strong>”
 at the mkiocccentry repo.</p>
+<p>However, an <strong>IMPORTANT NOTE</strong>: if you run the program outside the repo
+directory (specifying the absolute or relative path to the tool) and you
+have not installed the tools then you will have to specify the options for the
+tools that are required like <code>chkentry(1)</code>, <code>txzchk(1)</code> and <code>fnamchk(1)</code>. But
+even if you have installed them but some tools are out of date (in the install
+path) it will cause problems. Additionally, if you do not have the most recent
+version when submitting a tarball it will be rejected for not having the right
+versions of the tools. This is why you <strong>MUST</strong> make sure you have the most
+recent version of all the tools and you either run it from the repo directory
+itself OR you install them (<code>make install</code> as via <code>sudo</code> or as root).</p>
 <p>If the <code>mkiocccentry</code> tool indicates that there is a problem with your
 submission, especially if it identifies a <a href="next/rules.html#rule2">Rule 2</a>, or
 any other rule, related problem, you are <strong>strongly</strong> encouraged to revise and

quick-start.md

@@ -164,6 +164,17 @@ submission's directory. See the
 FAQ on "**[installing mkiocccentry](https://github.com/ioccc-src/mkiocccentry/blob/master/FAQ.md#install)**"
 at the mkiocccentry repo.
 
+However, an **IMPORTANT NOTE**: if you run the program outside the repo
+directory (specifying the absolute or relative path to the tool) and you
+have not installed the tools then you will have to specify the options for the
+tools that are required like `chkentry(1)`, `txzchk(1)` and `fnamchk(1)`. But
+even if you have installed them but some tools are out of date (in the install
+path) it will cause problems. Additionally, if you do not have the most recent
+version when submitting a tarball it will be rejected for not having the right
+versions of the tools. This is why you **MUST** make sure you have the most
+recent version of all the tools and you either run it from the repo directory
+itself OR you install them (`make install` as via `sudo` or as root).
+
 If the `mkiocccentry` tool indicates that there is a problem with your
 submission, especially if it identifies a [Rule 2](next/rules.html#rule2), or
 any other rule, related problem, you are **strongly** encouraged to revise and