Bug#308339: Wrong source package name

[Arnaud Vandyck]

Mon, 9 May 2005 19:47:46 +0200, 
Jeroen van Wolffelaar <jeroen@wolffelaar.nl> wrote: 

> On Mon, May 09, 2005 at 07:25:24PM +0200, Wolfgang Baer wrote:

[...]

>> Well, I think it was due to the old jakarta-log4j source package
>> which has currently a pending removal request and you have just
>> removed :-)
>> 
>> http://packages.qa.debian.org/j/jakarta-log4j.html
>
> Right, but you can instead just supersede that package by a new upload
> building other binary packages, thus completely rendering the go via
> ftp-master unneeded -- that was my point. Library name transitions would
> otherwise always need to go via ftp-master, which would be one big mess.
>
> If the name stays like this, next time it'll be log4j1.3, log4j1.4,
> etc., each time requiring ftp-master intervention.  I'm saying the
> source package should always remain at log4j.

I don't understand how you manage libraries that have incompatible
API's? How do we do with ant? bsh? servlet? struts?

You mean creating a tarball with the two different versions of the lib?!
And why do you want we change the name of the source package when the
first one is removed?

I'm sorry, I don't understand your point.

-- 
  .''`. 
 : :' :rnaud
 `. `'  
   `-    
Java Trap: http://www.gnu.org/philosophy/java-trap.html