You are viewing a plain text version of this content. The canonical link for it is here.
Posted to docs-cvs@perl.apache.org by pg...@apache.org on 2006/07/08 03:10:27 UTC

svn commit: r420027 - /perl/modperl/docs/trunk/TODO

Author: pgollucci
Date: Fri Jul  7 18:10:26 2006
New Revision: 420027

URL: http://svn.apache.org/viewvc?rev=420027&view=rev
Log:
AFAIK these things are done

Modified:
    perl/modperl/docs/trunk/TODO

Modified: perl/modperl/docs/trunk/TODO
URL: http://svn.apache.org/viewvc/perl/modperl/docs/trunk/TODO?rev=420027&r1=420026&r2=420027&view=diff
==============================================================================
--- perl/modperl/docs/trunk/TODO (original)
+++ perl/modperl/docs/trunk/TODO Fri Jul  7 18:10:26 2006
@@ -55,7 +55,7 @@
 
 =for html <hr>
 <p><b>
-$Id: TODO,v 1.81 2002/10/14 09:38:07 pereinar Exp $
+$Id$
 </b></p>
 
 =cut
@@ -75,45 +75,6 @@
 - add option to select number of results per page.
 
 ====================================================================
-*** Updating process tuning ***
-
-I'm thinking to use cron to update the site, on let's say 6 hours
-basis. Currently I manually execute an update script which does:
-
- cd /www/perl.apache.org/preview/modperl-docs
- cvs up
- bin/build -f
- bin/makeindex (for search)
-
-since a complete site rebuild including pdf generation is a very heavy
-operation, for efficiency we need to extend the update mechanism to
-do:
-
-* build + makeindex only if cvs up indicated that things were
-  changed. That means that we need something like VCS::CVS to get the
-  control over cvs.
-
-futher optimizations:
-
-* rerun makeindex only if things under src/ have changed
-
-* run build -df only if things under tmpl/, src/images or lib/ have
-  changed
-* otherwise run build -d (without -f), the code will figure out what
-  should be updated by itself.
-
-If we do this, no one will need to ssh to the site and manually update
-the site.
-
-One thing to think about: what if something goes broken, e.g. someone
-has committed code to lib/ and didn't manually verify that everything
-builds properly. Then on the next automatic update, things go kaboom
-and the site could become unusable. Any ideas how to prevent this?
-Currently I haven't planned using cvs for the autogenerated site.
-
-Anybody can help me to replace the 4-liner update script with a more
-elaborate one?
-====================================================================
 
 Later:
 ------
@@ -149,13 +110,6 @@
   Jesse Erlbaum is going to write an article for a "Perl-related
   publication", but that probably means we're not getting it ;(
   http://mathforum.org/epigone/modperl/pahphucree/450BF163A931D4119C2B00D0B774183D3B24D5@exchange.vm.com
-
-- Waiting for Slava Bizyayev to submit tutorial on Gzip handling in
-  different browsers. See:
-   o http://mathforum.org/epigone/modperl/pendskumtwox
-   o http://mathforum.org/epigone/modperl/blexvarcho
-  STATUS: written, Slava is checking out some info and arguing with
-  Igor :-)
 
 - mod_perl history page in About section [Per Einar]
   STATUS: working on it



---------------------------------------------------------------------
To unsubscribe, e-mail: docs-cvs-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-cvs-help@perl.apache.org