The corner case where -V still matters is if a package that ships a symbols
file is built with a new toolchain, then installed and built against on an
old system using an old version of dpkg-shlibdeps. Do you think this use
case is irrelevant, and we should just stop using -V when converting to
Steve Langasek wrote:
The corner case where -V still matters is if a package that ships a symbols
file is built with a new toolchain, then installed and built against on an
old system using an old version of dpkg-shlibdeps. Do you think this use
case is irrelevant, and we should just stop
* Joey Hess [Thu, 27 Dec 2007 11:33:56 -0500]:
Adeodato Simó wrote:
Now that symbol files are here, I think it could make sense to have a
smart mode for dh_makeshlibs were the shlib version is determined as
the highest version that appears in the symbols file. This would allow
for a
Package: debhelper
Version: 5.0.63
Severity: wishlist
Hello.
Now that symbol files are here, I think it could make sense to have a
smart mode for dh_makeshlibs were the shlib version is determined as
the highest version that appears in the symbols file. This would allow
for a tight shlibs file,
Adeodato Simó wrote:
Now that symbol files are here, I think it could make sense to have a
smart mode for dh_makeshlibs were the shlib version is determined as
the highest version that appears in the symbols file. This would allow
for a tight shlibs file, without the need to maintaining the
5 matches
Mail list logo
