Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Received-SPF: neutral (hermes.apache.org: local policy)
Date: Thu, 18 Nov 2004 06:45:12 -0600
From: QM <qm300@brandxdev.net>
To: Tomcat Users List <tomcat-user@jakarta.apache.org>
Subject: Re: Suggestion - upgrade scripts.
Message-ID: <20041118124512.GA17166@strange.dreamhost.com>
References: <000801c4ccb8$513c6da0$39e1a8c0@HOLODECK>
 <20041118000739.GB8416@strange.dreamhost.com>
 <000e01c4cd59$f0eaf550$39e1a8c0@HOLODECK>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <000e01c4cd59$f0eaf550$39e1a8c0@HOLODECK>
User-Agent: Mutt/1.3.28i

On Thu, Nov 18, 2004 at 10:32:33AM +0000, Andoni wrote:
: Ok, I have been playing around with this idea. What I would use most would
: not so much be an upgrade script between versions but an upgrade script
: between sub-version. Or maybe even just a list of the files that have
: changed in a sub-version upgrade, and a copy of each one.

Given the Apache license, you're more than able to create and distribute
such an "upgrade" package yourself.  As there are no roadblocks between
you and your goal, why not give ti a shot?

I personally prefer a different upgrade philosophy, but this certainly
is a situation in which we can all do what we want without affecting
anyone else. ;)

-QM


-- 

software  -- http://www.brandxdev.net
tech news -- http://www.RoarNetworX.com


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org