> From: Justin Ross [mailto:[email protected]] > > On Mon, 26 Apr 2010, Jonathan Robie wrote: > > > On 04/26/2010 03:22 PM, Justin Ross wrote: > >> > >> Shuttling generated docs through subversion seems > unnecessary. Any > >> script > >> that can check for a change in a generated document can > just as easily > >> check for a change in a source document. The only > difference after that is > >> performing the generation, true? > > > > I discussed this with #asfinfra earlier today. They won't run our > > build > > system on their server. Their system is happy to copy a > generated file over > > when we check it in, but not to build the system itself. > > > > Here's an excerpt from our conversation: > > > > <jrobie> i.e., instead of checking in the artifacts, i check in a > > makefile or > > ant file that builds the artifacts, it has to run on my > system, you run it on > > the client and then copy the artifacts over? > > <joes4> no > > <joes4> you're not running arbitrary programs on our > frontline webserver > > <joes4> we don't even allow cgi > > <joes4> telling me you won't blame me for your mistakes doesn't help > > <jrobie> so installing, say, xslt, docbook, fop, doxygen, > epydoc ... that's > > not going to happen > > <joes4> the public will always blame the asf > > > > You can try to convince Joe ;-> > > I think avoiding running programs on the frontline webserver > is perfectly > reasonable. However, I don't think that quite argues against > a script. > > We just need to figure out (A) where to run it and (B) how to > schlep the > results. B is the more important one, since it's not too > hard to scare up some cycles.
I think that automatically publishing web content based on source check-ins is a bit too automagic for consistency and correctness to be maintained. Also, I can imagine that there are source check-ins that should not generate web updates (they're intermediate, testing, may need review, etc.). I think it is always safer to have a person generate web-destined content and check it before sending it to the live web. -Steve --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
