Re: Tomcat 10 packaging

[Emmanuel Bourg <ebourg@apache.org>]

Le 28/09/2022 à 17:53, Emmanuel Bourg a écrit :

> Pros:
> - no need to create a new package, replacing tomcat<n> with tomcat<n+1> 
> everywhere, and then wait for the NEW queue
> - unique packaging repository
> - no more transition, replacing the libtomcat<n>-java dependency with 
> libtomcat<n+1>-java everywhere (currently about 15 packages)
> - no need to install tomcat<n+1> and transfer /etc/tomcat<n> to 
> /etc/tomcat<n+1> when upgrading Debian
> - the log files and the deployed web applications also remain at the 
> same place

There is another benefit of a versionless package: backport continuity. 
When the tomcat<n+1> package replaces tomcat<n> in testing/unstable, 
it's no longer possible to update the tomcat<n> backport in stable 
(because the version must exist in testing). With a unique tomcat 
package we can keep updating the stable backport even after upgrading to 
a more recent release in testing.

(this is just a note for later discussions)

Emmanuel Bourg