Gregory (Grisha) Trubetskoy wrote:
On Tue, 7 Jun 2005, Jim Gallacher wrote:
What's the mechanism for this, since the generated docs are not in
subversion?
The docs _are_ in subversion, but in .tex format. The html is included
in the distribution tar file for convenience, but I don't think it'd
make sense to have both tex and html in svn.
Yes, I know the docs are in subversion. I was thinking of the html + pdf
stuff. But you are right, no need for a copy of these in the repository,
since they are in effect compiled from the source.
Presumably, when the release is ready you'll create a branch, and then
the docs will get committed to that branch?
I think that generating the docs is the trickiest part of making the
release tarball, so you might as well just do the whole thing :-) Or I
could do it, but I'd really sleep better knowing that I am not alone
able to create a tarball.
Can do. Your earlier suggestion of putting the release instructions in a
separate file makes sense. I had looked in Doc/Makefile when trying to
generate the docs, but had not read all the way to the bottom!
Same question for the generated psp.c (using flex) and configure,
generated from configure.in with autoconf.
The generated psp.c is there just in case you don't have flex
(especially because a specific version of flex is required). I guess
it's similar to ./configure - in theory there is no need to keep it
since it is autogenerated from configure.in, but most projects do it
anyway...
I think it's nice to include both ./configure and psp_parser.c so that
people don't need to track down the proper version of flex and autoconf.
Regards,
Jim
