You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Jeff Turner <je...@apache.org> on 2002/11/19 13:20:37 UTC
[RT] Forrest update system (Re: Docbook DTD)
On Tue, Nov 19, 2002 at 06:59:05PM +1100, Peter Donald wrote:
> On Sat, 16 Nov 2002 21:48, David Crossley wrote:
> > > * add docbook4.1.2 into catalog
> >
> > Perhaps Forrest should distribute these by default, and
> > maybe the XHTML stuff too.
>
> +1
>
> Would make my life easier and both of those formats are relatively well
> supported/ "standards based" formats ;)
Hmm.. Docbook stylesheets (xhtml) and DTDs are 1.36mb in total.
How about a more modular apt-get kind of system, where you type
'forrest-update docbook' to have the Docbook DTDs and stylesheets
installed?
An update system could also be used to update Forrest installs. No need
to download 12mb to go from 0.2 to 0.2.1, when only one .bat script
changes, just type 'forrest-update 0_2_1' and the changed files will be
patched.
I have implemented a prototype of this for Anteater, described at:
http://aft.sourceforge.net/updates.html
Eg, typing 'anteater-update xhtml-schema' downloads the XHTML RNG schemas
from James Clark's site, which can then be used in Anteater tests.
The Anteater system is (piecewise) really simple:
- 'anteater-update' runs a local bootstrap Ant script which..
- downloads a driver Ant script from ViewCVS, and runs it..
- which presents the user with a selection of 'updates'. When the user
chooses one, the script gets the update Ant script from ViewCVS and
runs it..
- the update script then does whatever to update the local installation.
Typically this involves fetching an updated file from ViewCVS (or
James Clark's site in the case of xhtml-schema-install.xml) and
applying it to the local install.
Only one small bootstrap Ant script and 'anteater-update' shell script
need be bundled with the system initially. Everything else, including
the list of updates, is external and we can update it at any time, by
committing a newer version to CVS (hence appearing in ViewCVS).
I'm not proposing to do this right now.. just floating the idea. What
I'd _really_ like to have is a .deb or RPM-like system where signed jars
contain updates, and a META-INF/control.xml Ant script directs how to
apply the update. Updates would be applied in a sandbox (after verifying
the jar signature) to keep things secure. Perhaps JWS has something like
this.. so many wheels to reinvent, so little time :P
--Jeff
> --
> Cheers,
>
> Peter Donald
> --------------------------------
> These aren't the droids you're
> looking for. Move along.
> --------------------------------
Re: [RT] Forrest update system (Re: Docbook DTD)
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Bertrand Delacretaz wrote:
> On Tuesday 19 November 2002 13:20, Jeff Turner wrote:
>
>>. . .
>>I have implemented a prototype of this for Anteater, described at:
>>
>>http://aft.sourceforge.net/updates.html
>>. . .
>
>
> Great idea to use downloadable ant scripts for this - I like it!
>
> I think this has a much broader range of uses than just Forrest.
> If you're thinking of adding add jar signature checking and the like, maybe
> this should be a separate project or an ant extension?
http://www.krysalis.org/centipede/
http://krysalis.sf.net/
Centipede is meant to have such a system, and it's based on Ant.
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: [RT] Forrest update system (Re: Docbook DTD)
Posted by Bertrand Delacretaz <bd...@codeconsult.ch>.
On Tuesday 19 November 2002 13:20, Jeff Turner wrote:
>. . .
> I have implemented a prototype of this for Anteater, described at:
>
> http://aft.sourceforge.net/updates.html
>. . .
Great idea to use downloadable ant scripts for this - I like it!
I think this has a much broader range of uses than just Forrest.
If you're thinking of adding add jar signature checking and the like, maybe
this should be a separate project or an ant extension?
-Bertrand
Re: [RT] Forrest update system (Re: Docbook DTD)
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Jeff Turner wrote:
> On Wed, Nov 27, 2002 at 05:25:37PM +1100, David Crossley wrote:
> ...
>
>>>I'm not proposing to do this right now.. just floating the idea. What
>>>I'd _really_ like to have is a .deb or RPM-like system where signed jars
>>>contain updates, and a META-INF/control.xml Ant script directs how to
>>>apply the update. Updates would be applied in a sandbox (after verifying
>>>the jar signature) to keep things secure. Perhaps JWS has something like
>>>this.. so many wheels to reinvent, so little time :P
>>
>>This would be an excellent capability for Forrest to have.
>>
>>Is it possible for Anteater to be distributed with Forrest?
>>Then Forrest can just utilise various Anteater capabilities
>>and we can concentrate on inventing other wheels.
>
>
> Anteater currently has just a straightforward chained Ant script system,
> not the fancy signed jar system described above.
>
> Nicola mentioned being able to download skins.. that is another good
> application of an update system: 'anteater-update <skin name>'.
>
> The driver is a 20 line script.. I'll check it in and we'll see if it
> proves useful.
look at the ruper task in krysalis. Ruper=Remote Updater.
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: [RT] Forrest update system (Re: Docbook DTD)
Posted by Jeff Turner <je...@apache.org>.
On Wed, Nov 27, 2002 at 05:25:37PM +1100, David Crossley wrote:
...
> > I'm not proposing to do this right now.. just floating the idea. What
> > I'd _really_ like to have is a .deb or RPM-like system where signed jars
> > contain updates, and a META-INF/control.xml Ant script directs how to
> > apply the update. Updates would be applied in a sandbox (after verifying
> > the jar signature) to keep things secure. Perhaps JWS has something like
> > this.. so many wheels to reinvent, so little time :P
>
> This would be an excellent capability for Forrest to have.
>
> Is it possible for Anteater to be distributed with Forrest?
> Then Forrest can just utilise various Anteater capabilities
> and we can concentrate on inventing other wheels.
Anteater currently has just a straightforward chained Ant script system,
not the fancy signed jar system described above.
Nicola mentioned being able to download skins.. that is another good
application of an update system: 'anteater-update <skin name>'.
The driver is a 20 line script.. I'll check it in and we'll see if it
proves useful.
--Jeff
> --David
>
>
Re: [RT] Forrest update system (Re: Docbook DTD)
Posted by David Crossley <cr...@indexgeo.com.au>.
On Tue, 2002-11-19 Jeff Turner wrote:
> Peter Donald wrote:
> > David Crossley wrote:
> > > Peter Donald wrote:
> > > > * add docbook4.1.2 into catalog
> > >
> > > Perhaps Forrest should distribute these by default, and
> > > maybe the XHTML stuff too.
> >
> > +1
> >
> > Would make my life easier and both of those formats are relatively well
> > supported/ "standards based" formats ;)
>
> Hmm.. Docbook stylesheets (xhtml) and DTDs are 1.36mb in total.
>
> How about a more modular apt-get kind of system, where you type
> 'forrest-update docbook' to have the Docbook DTDs and stylesheets
> installed?
>
> An update system could also be used to update Forrest installs. No need
> to download 12mb to go from 0.2 to 0.2.1, when only one .bat script
> changes, just type 'forrest-update 0_2_1' and the changed files will be
> patched.
>
> I have implemented a prototype of this for Anteater, described at:
>
> http://aft.sourceforge.net/updates.html
>
> Eg, typing 'anteater-update xhtml-schema' downloads the XHTML RNG schemas
> from James Clark's site, which can then be used in Anteater tests.
>
> The Anteater system is (piecewise) really simple:
>
> - 'anteater-update' runs a local bootstrap Ant script which..
> - downloads a driver Ant script from ViewCVS, and runs it..
> - which presents the user with a selection of 'updates'. When the user
> chooses one, the script gets the update Ant script from ViewCVS and
> runs it..
> - the update script then does whatever to update the local installation.
> Typically this involves fetching an updated file from ViewCVS (or
> James Clark's site in the case of xhtml-schema-install.xml) and
> applying it to the local install.
>
> Only one small bootstrap Ant script and 'anteater-update' shell script
> need be bundled with the system initially. Everything else, including
> the list of updates, is external and we can update it at any time, by
> committing a newer version to CVS (hence appearing in ViewCVS).
>
>
> I'm not proposing to do this right now.. just floating the idea. What
> I'd _really_ like to have is a .deb or RPM-like system where signed jars
> contain updates, and a META-INF/control.xml Ant script directs how to
> apply the update. Updates would be applied in a sandbox (after verifying
> the jar signature) to keep things secure. Perhaps JWS has something like
> this.. so many wheels to reinvent, so little time :P
This would be an excellent capability for Forrest to have.
Is it possible for Anteater to be distributed with Forrest?
Then Forrest can just utilise various Anteater capabilities
and we can concentrate on inventing other wheels.
--David