From dev-return-1964-apmail-perl-dev-archive=perl.apache.org@perl.apache.org Fri Nov 02 11:42:47 2001 Return-Path: Delivered-To: apmail-perl-dev-archive@perl.apache.org Received: (qmail 83329 invoked by uid 500); 2 Nov 2001 11:42:45 -0000 Mailing-List: contact dev-help@perl.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@perl.apache.org Received: (qmail 83302 invoked from network); 2 Nov 2001 11:42:44 -0000 Message-ID: <00b901c16393$7b121710$0b0b0b0a@i.ecos.de> From: "Gerald Richter" To: Cc: "Nathan Torkington" , References: <15297.48528.281000.422063@gargle.gargle.HOWL> <15311.24078.98000.705215@gargle.gargle.HOWL> <38926249.1003430730@[0.0.0.0]> <15311.27165.127000.416600@gargle.gargle.HOWL> <3BCFA877.5010004@stason.org> <15316.38858.553000.411526@gargle.gargle.HOWL> <3BD6894C.9040409@stason.org> <3BE27FD3.80603@stason.org> Subject: Re: moving modperl-site rep into modperl-docs rep Date: Fri, 2 Nov 2001 12:42:24 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > > With my proposal we will have to do: > on our machines: > 1. cvs up > 2. apply changes > 3. cvs ci > on apache.org: > 4. cvs up > 5. bin/build > > so there is one extra step to do. Is this OK? > For the modperl site that would be ok for me. (Since everything is done for me by a Perl script, is doesn't matter if there is an addtional step :-) > issues: > > - need to install TemplateToolkit and a few other packages on > apache.org :( I guess we can do it locally, I don't want to pester Brian. Should be no problem > - the package handles links so we have no problem linking to e.g. > perl.apache.org/dist/ ok, so we have the possibility to use content that is not part of the docset > - embperl site, I suppose it can be folded into the docset, if Gerald > doesn't mind. For the Embperl site I have slightly different plans. There is a redesign already on the road for a couple of time, I just didn't have the time to finish and upload it. I have followed the discussion about the docset thing. I like your docset idea, but I have also own ideas which build on the new features of Embperl (namly XML & XSLT) Hopefully your docset tool is modular enough that TT is only used for rendering, so it would be maybe possible to plug Embperl, instead of TT ? (of course it doesn't would look nice if the Embperl website says "powered by TemplateToolkit :-) so for now we maybe can simply keep the modperl-site cvs and use it only for Embperl (and maybe the dist dir). Gerald ------------------------------------------------------------- Gerald Richter ecos electronic communication services gmbh Internetconnect * Webserver/-design/-datenbanken * Consulting Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz E-Mail: richter@ecos.de Voice: +49 6133 925131 WWW: http://www.ecos.de Fax: +49 6133 925152 ------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org For additional commands, e-mail: dev-help@perl.apache.org