Journal/arXiv submission archive

[GoogleCodeExporter]

I would like to see a target that prepares a (.zip or .tgz) archive for
submission to arXiv or to a journal. It should include the main .tex file,
the .bbl file (not .bib!), and the compiled images in their final format.

Original issue reported on code.google.com by f.pol...@gmail.com on 9 Apr 2010 at 8:24

[GoogleCodeExporter]

For requests like these, I typically ask people to get the rules right in their 
Makefile.ini file first, then we have 
something concrete to talk about.  This makes it easier to decide whether it is 
worth adding more complexity to 
the already amazingly complex makefile :)

So, if you can put something together, at the very least a list of dependencies 
for the said .zip or .tgz file, then 
that would be helpful.  For example, does it also need to include index files?  
(etc.)

Original comment by shiblon on 9 Apr 2010 at 4:19

• Added labels: Priority-Low, Type-Enhancement
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

I will try to hack a couple of rules into Makefile.ini, thanks.

Original comment by f.pol...@gmail.com on 10 Apr 2010 at 11:03

[GoogleCodeExporter]

I tried to write some generic rules, but I seem unable to figure out how the 
graphics dependencies are generated and handled -- sorry but this Makefile 
seems just too complicated for me to understand. :)

I'll try to write down what dependencies I'd like to have, based on what 
journals and arxiv seem to ask:
-main .tex file and all the .tex dependencies to be included
-.bbl (not .bib)
-final form for all graphics (pdf/eps)
-.ind/.aux/other intermediate stuff is usually not needed

All shipped into a .zip/.tgz archive.

Original comment by f.pol...@gmail.com on 9 Jun 2010 at 1:37

[GoogleCodeExporter]

An automatic dependency is always created for graphics.  So, if you have a file 
called "myfile.tex", you can depend on the target myfile._graphics and it will 
build those.

Unfortunately, there's no easy way to expand that into a list of files.  
However, it is relatively easy to suck them out of myfile.d using something 
like 'sed'.

In fact, all of the dependencies for a given compilation are found in the .d 
file.  It might be worth taking a look at your .d file output (just the 
top-level one named after your main file) to see what it contains.  It should 
contain necessary class files, style files, imported tex files, and all 
graphics and index files.  That will at least give us a concrete starting 
point.  If all of the required dependencies are mentioned in there, it will be 
really pretty easy to add a myfile._arxiv.zip target (or similar) that depends 
on them.

Original comment by shiblon on 9 Jun 2010 at 1:45