Adopting libapache-mod-jk and libapache2-mod-jk2

[Michael Koch]

On Wed, Sep 07, 2005 at 11:24:47AM +0200, Wolfgang Baer wrote:
> Guus Sliepen wrote:
> > On Tue, Sep 06, 2005 at 09:40:42PM +0200, Wolfgang Baer wrote:
> 
> > Thanks! So far, I can't see anything wrong with the packages. Personally
> > I'm glad to see CDBS isn't used anymore. It builds without problems
> > (under sarge as well). I will test the packages tomorrow with a real
> > setup (apache2, tomcat5, Java servlets).
> 
> That would be great as I only tested with tomcat4/apache1.3 and JSP
> examples and have no other setup available.
> 
> >>One thing currently not addressed is a possible upgrade path
> >>from the deprecated libapache2-mod-jk2 package. I am not sure
> >>if this is possible at all because of different configuration
> >>files - comments are welcome !
> > 
> > AFAIK there is no Supersedes: option for control files, but I wouldn't
> > Conflict, Provide or Replace libapache2-mod-jk2. There is no technical
> > reason why the packages couldn't coexist, and since the configuration
> > files have a different format you can't just replace jk2 with jk.
> 
> Sure they can coexist - however we want to remove libapache2-mod-jk2
> from the archive after mod-jk for apache 2 will be availabe. Therefore
> anything which would inform users to change to the new package would
> be good ...

The normal location for this is an entry in the NEWS.Debian file. This
is what the policy recommends for this. This file is specially handled by
several tools like apt-listchanges and will prompted to the use on
install/upgrade once.

Personally I would add a debconf dialog too but that is seen as abuse from
many DDs so don't do it.


Michael
-- 
Escape the Java Trap with GNU Classpath!
http://www.gnu.org/philosophy/java-trap.html

Join the community at http://planet.classpath.org/