Re: [Gnucap-devel] patches to gnucap-2006-07-08

[al davis]

On Thursday 17 August 2006 08:00, Stuart Brorson wrote:
> > but why ever totally remove the man/html directory?  Why
> > not just remove all of the generated files in there?  Or
> > does HeVeA have some issue with that?
>
On Thursday 17 August 2006 08:00, Stuart Brorson wrote:
> Pardon me for butting in here.  I basically agree with Dan. 
> In other projects I've seen, an empty directory for stuff yet
> to be built will still have the Makefile.am in it to enable
> building the directory's contents using the GNU build stuff. 
> It makes the lives of the developers (and downstream users)
> sooooo much easier than trying to fool the automake system
> some other way.

It is something else to maintain.

Why is that file needed at all?  All it does is list the files 
so they will be in the distribution file.  Since the whole 
thing is generated, the file names are not known ahead, so it 
is a wildcard list anyway.  Why not just list "html/*" in the 
parent's Makefile?


The same goes for the data  (old ugly name "==") in the test 
subdir, except there, it wasn't generated as that name.  I have 
a bunch of test data directories, for things like comparing 
today's version to yesterday's, or to see the effect of a code 
change.

I have another question on this one ....  Since there may be 
several, what should be enclosed?  I haven't paid much 
attention to this, but now as the amd64 becomes more popular, 
maybe both amd64 and intel versions should be included.

Maybe I should explain how I actually use those files.



Another change for the next snapshot ....  It can also 
generate "info" format and plain text, using hevea.
And ...  With a grep hack, I managed to suppress those nuisance 
hyperref warnings.  If anyone knows a better way to get rid of 
those warnings, let me know.  The best way is to fix what they 
are warning about, but I have no clue how to do that.