[task #15674] ArXiv anc/ directory - publication checklist

[Boud Roukema]

Follow-up Comment #2, task #15674 (project reproduce):

There are two different useful effects of using the _anc/_ directory
with arXiv:

(i) it is clear to the reader of the default abs/yymm.xxxxx
URL that extra files are available, in particular, it looks like the first
five files 
(alphabetically, digits  first, then upper case, then lower case) 
are shown and the rest as _(N-5) other files_;

(ii) the files in _anc/_ are allowed to have the executable flag set
(presumably because there's no risk to the ArXiv system of
trying to execute the files).

In the source format of 2006.03018v1, I see:

    5  -rw-rw-r--    root/root      16452 project
...
-rw-rw-r--    root/root       2963 reproduce/software/shell/git-pre-commit
   39  -rw-rw-r--    root/root       1940 reproduce/software/shell/bashrc.sh
   40  -rw-rw-r--    root/root       2377
reproduce/software/shell/git-post-checkout
   41  -rw-rw-r--    root/root       6276
reproduce/software/shell/pre-make-build.sh
   42  -rw-rw-r--    root/root      45443
reproduce/software/shell/configure.sh
   43


Effect (ii) solves the executability privilege problem if we put the 
full set of files in anc/ - The
user will be able to do _./project configure_ without having to do 
_chmod u+x project_ and _chmod u+x reproduce/software/shell/*_ .

With 1902.09064, I was only thinking of (ii) - I noticed (i) at some point of
the
submission process, but (i) wasn't a motivation in itself.
The main motivation for (ii) was to have everything within a
single directory, with a minimum number of steps for the user.

My tentative plan for submission for any particular research paper
is to have the full maneage distribution
inside of _anc/_, and only _paper-full.tex_ (after usage of _latexpand_) 
and the _tex/_ figure subdirectories _img/_ (and _tikz/_ if used) in the top
directory (top = top directory of tar.gz package). Probably 
_README*_ and _COPYING_ should also be in the top directory, 
either as real files or as sym links.


    _______________________________________________________

Reply to this item at:

  <https://savannah.nongnu.org/task/?15674>

_______________________________________________
  Message sent via Savannah
  https://savannah.nongnu.org/