Philip M. Gollucci wrote:
> Adam Prime wrote:
>> i just sat down to take a look at this, the top page is not in the
>> repository, nor is it generated by the build script.  So i'm guessing
>> that the cron the syncs the files does not remove things after they are
>> removed from the repo.  The page doesn't appear to show up in the
>> swish-e's search results, but it is indexed by google.
> Adam et al,
> 
> The rsyncs to the other computers run hourly.  And 1 time daily they do a
> rsync --delete.  The delete is only daily b/c it has to do a full tree
> walk over all 70 some ASF problems.
> 
> Adam, if you login to people.apache.org and follow the sudo instructions
> for perlwww.  Then, /www/perl.apache.org You can then tweak it.  It
> should be an svn checkout where the crons have been run.
> 
> If you are lacking permissions let me know, and I'll get that fixed.
> 
> Obviously, I could have done this in a few seconds but spreading the
> knowledge is a good thing (tm)

I have archived the entire Apache directory and the Apache.html/pdf from
docs/2.0/api into ~/api_old.  I've added a README file to that directory
indicating when, and what those files are.  I thought it'd probably be
better to not blow them right away, even though i'm pretty confident
that that would be ok.

I think it would make sense to add an option to the build script which
will build from a clean slate occasionally, this should keep this sort
of problem from occurring again.

Thoughts?

Adam

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to