Theoretically, the documentation should be installed automatically when
you do `make install'. Users shouldn't have to look for it separately.

That's of course a problem: the CVS source doesn't contain any
documentation and most people are not set up to rebuild it. Ignoring
missing files isn't good either because that would pose problems to people
that do try to rebuild it.

I could imagine some kludgery like not automatically installing the
documentation if there's a subtle hint, like the existence of a "CVS"
subdirectory, or perhaps something more explicit, that wouldn't be in the
distribution. Still seems ugly though.

Any better ideas?

I would also like to renew my campaign for shipping the HTML documentation
in non-compressed/tarred form. It seems to be no longer necessary since
these files are gone from CVS. Also, this way users could read them still
in the install tree (if the flat text INSTALL doesn't suit them, for
example).


-- 
Peter Eisentraut                  Sernanders vï¿½g 10:115
peter_e@gmx.net                   75262 Uppsala
http://yi.org/peter-e/            Sweden


Wed, 12 Jul 2000 02:24:07 +0200 (CEST)
Peter Eisentraut <peter_e@gmx.net>
How to handle documentation installation