Please release 0.99.18-2 (was: jed with API version in package name)

[G. Milde]

On 22.06.06, Jörg Sommer wrote:
 
> I asked on debian-devel about the usage of the conflict field and got the
> answer to fix this problem in jed-extra, e.g. not set the conflict field
> in jed or xjed

OK. This is what we did in 0.99.18-2.

> and the other suggestion to introduce pseudo names with the api
> version.
> 
> jed: Provides: jed-slang-2
> jed-extra: Depends: jed-slang-2
> 
> I think this is a really interesting idea, but I don't think we get a
> great benefit from it. I think the next big SLang version jump happens in
> 5 years. I wouldn't do it. What do you think?

 * Keep it in mind as an additional option.
 
 * Even this would not solve our problem, that the existing jed-extra
   doesnot work after upgrading jed or xjed.
   
   While the conflict belongs to jed-extra, it is not present in
   jed-extra/testing. 
   
   There doesnot seem to be a provision for this case in the Debian
   dependency system.

   Well, we could upload a new jed-extra (0.1.8-1) with a versioned
   confict to jed|xjed (>=0.99.16) added to the control file.
   
 * However, while jed-extra (slang-1) will fail to work jed|xjed
   (0.99.18), it will not break them. (The renaming of jed-init.d/ to
   jed.d/ has the side-effect that the configuration files of the old
   jed-extra are simply ignored.)
   
So, my suggestion would be to release jed, xjed, and jed-common in
version 0.99.18-2 to /testing and try to follow with jed-extra as soon
as possible to get both of them into the next release.

Günter