Didier Dubois wrote:
>
> Daniel Rall wrote:
> >
> > Christopher Elkins wrote:
> > > [snipped jon]
> > > > once we have stable version of this stuff, we should probably also build a way
> > > > for people to migrate to newer versions by doing upgrades. something like:
> > > >
> > > > newapp.sh scarab upgrade
> > > >
> > > > that way, it would take an existing application and upgrade it to the latest
> > > > and greatest TDK.
> > > >
> > > +1
> >
> > +1. I vote that this should become part of the build process itself.
> > Upgrade scripts should be checked in with every commit that could break
> > someone's working Turbine instantiation. Running build-turbine.sh
> > should automatically run the appropriate Ant tasks to upgrade a Turbine
> > instantiation from one version to another. This is somewhat difficult
> > in that just knowing the Turbine version doesn't really provide a known
> > state, but it would be nice to have a program that would at least *try*
> > to automate the upgrade, and let you know if you need to take manual
> > steps if the upgrade could not be completed automatically. Let me know
> > if you think I'm dreaming guys. ;)
>
> +1.
> Suggestion: what about using a system like rpm? Cold this makes sense?
> Didier
>
The problem with RPM is that it is not fully cross-platform. Obviously
it works for Linux and I know it works for Solaris but what about Win
users?
Beyond that though, I am +1 on the suggestion. I would like to see a
Turbine app 'know' about itself in such a way where it could be queried
and return the appropiate version information. That would allow
upgrades to occur seemlessly...
josh
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
