Re: gEDA-dev: What should be included in the dist file?

[Dan McMahill <dan@xxxxxxxxxxxx>]

John Luciani wrote:
> On 8/16/06, al davis <ad106@xxxxxxxxxxxxxxxx> wrote:
>
> > Documentation:
>
>
> 1. HTML files?  yes (nice for quick reference using a browser)
> 2. DVI files?   no (use the pdf or compile the La/TeX files
> 3. PDF files?   yes (nice for printing and scaling pages)
> 4. PS files?    no (use the pdf or compile the La/TeX files)

One comment about the .dvi files.  Distributing them can make life 
simpler in terms of the build system.  It is pretty easy to write rules 
like:

foo.pdf: foo.dvi
	${DVIPDFM} .....

foo.dvi: foo.tex
	${LATEX} ....

with perhaps some extra conditionals for the existance of those tools. 
Now if you don't distribute the .dvi file, you need some sort of extra 
magic to avoid trying to rebuild the .dvi since the dependencies say you 
need it.  I guess you can do something like

Right now I have:

# run it twice to fix the toc.
gnucap-man.dvi: $(TEXFILES)
if MISSING_LATEX
        @echo "WARNING:  latex was not found on your system but"
        @echo "          $@ is out of date and needs to be"
        @echo "          rebuilt from the LaTeX .tex files. Changes to"
        @echo "          the .tex files will be ignored."
else
        env TEXINPUTS=$(srcdir): ${LATEX} $(srcdir)/gnucap-man
        env TEXINPUTS=$(srcdir): ${LATEX} $(srcdir)/gnucap-man
endif


and I guess you could put 'touch $@' at the end of the MISSING_LATEX 
section and then you'd also have to put a MISSING_LATEX conditional 
around the rule for building the .pdf from .dvi.  All in all, I'd rather 
in general ship the .dvi file.


> > What about generated "source" files?
> > These are files in C or whatever, that look like source, but are
> > actually generated.  My experience is that to include them tricks
> > people into thinking they are source, causing more problems, but may
> > allow them to build when a translation program (m4, awk,
> > gnucap-modelgen, autoconf) is not available.
>
>
> Requiring basic tools like m4, awk, etc. does not seem
> like an unreasonably requirement.

I agree but I don't put autoconf in the "basic tools" category.  But one 
should never need that unless you're editing configure.ac but if you're 
doing that then I no longer feel bad about requiring it.  Normal end 
users should not need it though so I certainly believe generated 
'configure' goes in the distfile.

-Dan



_______________________________________________
geda-dev mailing list
geda-dev@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev