Bug#321241: libkpathsea4-dev: Needs a README.Debian
On 22.08.05 Frank Küster (frank@debian.org) wrote:
> Hilmar Preusse <hille42@web.de> wrote:
Hi,
> > I guess
> > http://lists.debian.org/debian-tetex-maint/2004/03/msg00181.html
>
> Yes, indeed. Maybe even put that URL into the text.
>
suggestion attached.
> > I try to write an entry for Readme.Debian for that. Should we put it
> > into News.Debian instead or will it not be displayed during fresh
> > install?
>
> If you're speaking about apt-listchanges, NEWS.Debian is only
> displayed upon upgrade.
>
And only if apt-listchanges is installed and configured the right
way. The default is to display the changelog and the News.
Put it into README.Debian.
> I don't know whether libkpathsea4-dev will automatically be
> installed if libkpathsea-dev from teTeX-2.0.2 (which it provides)
> is installed. If that is the case (and not only for aptitude, but
> also for apt-get), and if apt-listchanges also regards this as an
> upgrade, then NEWS.Debian makes sense; otherwise just
> README.Debian.
>
Hmm, I guess the upgrade should work. If apt-listchanges will be so
clever to consider this to be an upgrade should be asked to Matt
Zimmerman. Will do so.
H.
--
sigmentation fault
Why a new soname of libkpathsea in teTeX 3.0?
---------------------------------------------
We're just quoting Olaf Weber, the author of web2c. The full message can be
found on:
http://lists.debian.org/debian-tetex-maint/2004/03/msg00181.html
"libkpathsea moved from using klibtool (a web2c-specific libtool-like hack)
to libtool. As a result it acquired a new soname.
libkpathsea was not designed to work well as a shared library, and has
numerous flaws in that area -- in particular, too many internals are
exposed, and too much is hard-coded."
Olaf does not expect too many changes in the API of the libkpathsea between
teTeX 2.0.2 and 3.0 so just relinking the programs should be sufficient.
However that is not really predictable.
"So at present my advice is that it's better to be safe than sorry, and
enforce that the version of libkpathsea matches the program's version."
A new redesigned libkpathsea, which is really a shared lib, is on his TODO
list, but he can't say when it will be released.
Reply to: