Gilles Chanteperdrix kirjoitti:
Heikki Lindholm wrote:
 > Gilles Chanteperdrix kirjoitti:
> Indeed. But this is the special attention I'm talking about ;) I'm still > not convinced about the "need 'em for the release" reasoning. Let's put > it this way: what trouble would it bring, if we had "dist" always > generate docs for a release (and not have them in the repo)?

Allows to share the load during releases: I generate the doc, using the
"generate-doc" target in the doc directory, run svn commit to put them
in the repository. Then Philippe runs svn update and make dist. As I
said, it allows to have a separate maintenance of documentation and

Hehe. So Philippe's machine would choke, if it had to generate the docs, too(?) And since most(?) of the docs comes from the sources, you don't actually edit them by hand now do you? So what does maintaining mean here?

Having the generated documentation in svn repository also allows us to
copy it to the documentation directory of the download zone from a
script run by cron.

Ok, this makes sense. But could be done by other means, too, I guess.

-- Heikki Lindholm

Reply via email to