>
> 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
|