> > we could move the english docs out of pgsql itself and into this module
> > too, as:
> > pgsql-docs/en
> Hmm, I'm not sure that that's a good idea; seems it would lose the
> coupling between versions of the source and versions of the
> documentation.
We could (and should, imho) leave the English docs where they are, but
they could be included as a module in the pgsql-docs repository.
> Anyone have experience with managing this sort of situation under CVS?
Yes.
> Is separate tree or combined tree better?
I would suggest defining a "pgsql-docs" module, which might contain the
actual code for non-English docs. We can define a logical module
"pgsql-en" which is included in the *logical* pgsql-docs module (the
latter also contains the *physical* pgsql-docs module).
We've done this on other projects. I can help set up the module
definitions (which are fairly simple when worked out, but perhaps not
trivial to derive from first principles. I'll steal the solution from
work I've done earlier ;)
- Thomas