Adopting libapache-mod-jk and libapache2-mod-jk2
Michael Koch
konqueror at gmx.de
Wed Sep 7 09:35:32 UTC 2005
On Wed, Sep 07, 2005 at 11:30:36AM +0200, Guus Sliepen wrote:
> On Wed, Sep 07, 2005 at 11:24:47AM +0200, Wolfgang Baer wrote:
>
> > > 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 ...
>
> How about after libapache2-mod-jk is accepted, you upload a new version
> of libapache2-mod-jk2 that displays a debconf warning that it is
> deprecated and that you should switch to libapache2-mod-jk in the near
> future?
Personally I would do something like this too but this is called
"debconf abuse" by many people and will result in at least "important" bugs.
Michael
--
Escape the Java Trap with GNU Classpath!
http://www.gnu.org/philosophy/java-trap.html
Join the community at http://planet.classpath.org/
More information about the pkg-java-maintainers
mailing list