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.
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.
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...
Grisha
