Bug#354507: libkpathsea3 should be removed

[Adrian Bunk <bunk@stusta.de>]

On Wed, Mar 01, 2006 at 05:25:09PM +0100, Frank Küster wrote:
>...
> > - people using self-compiled programs linked with libkpathsea (which 
> >   should be quite rare) can simply keep libkpathsea3 on their system
> >   no matter that it's removed from etch
> > - Debian doesn't keep two so-version of other libraries even in cases of
> >   more popular libraries
> 
> I think that we should not decide about the removal of libkpathsea3
> before we have managed to make it superfluous in Debian.  Consequently,
> I agree that my previous decision "keep in etch" was also wrong.  But I
> think we should wait until we know whether migrating Debian packages to
> libkpathsea4 presents any problems.  If it does, we can expect other old
> stuff around outside Debian that might still need it.
>...

AFAIK, there are no known API changes in libkpathsea4 and having both 
libkpathsea3 and libkpathsea4 available at the same time was only 
required to work around the known inability of testing to cope well 
with library transitions.

Now that teTeX 3.0 is in testing and these testing-specific issues are 
no longer an issue, would you expect any problems with simply renaming 
libkpathsea4-dev to libkpathsea-dev (and providing libkpathsea4-dev)?

> Regards, Frank

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed