The following commit has been merged in the master branch:
commit 38a294899b4baafa2f223ee0760a06641f8aa2b4
Author: Raphaël Hertzog hert...@debian.org
Date: Fri Jan 13 20:49:21 2012 +0100
deb-symbols(5): drop misleading spaces in the format description
diff --git a/debian/changelog
Raphael Hertzog hert...@debian.org writes:
On Mon, 02 Jan 2012, Russ Allbery wrote:
[...]
p
fileshlibs/file files were the original mechanism for
handling library dependencies. They are documented
in ref id=sharedlibs-shlibdeps. filesymbols/file files,
Russ Allbery r...@debian.org writes:
I tried sending a unified diff, but the new sections are largely
unreadable since they're intermixed with the old sections being removed.
Hence, for review purposes, here are the symbols and shlibs sections in
their entirety, followed by a diff for the
On Fri, 13 Jan 2012, Russ Allbery wrote:
For our example, the ttzlib1g/tt filesymbols/file file
would contain:
example compact=compact
* Build-Depends-Package: zlib1g-dev
/example
(Don't forget the leading space.)
What leading space are you
On Fri, 13 Jan 2012, Russ Allbery wrote:
+ p
+ example
+varlibrary-soname/var varmain-dependency-template/var
+[ | varalternative-dependency-template/var ]
+[ ... ]
+[ * varfield-name/var: varfield-value/var ]
+[ ... ]
+ varsymbol/var varminimal-version/var[
Raphael Hertzog hert...@debian.org writes:
There is no leading space before the *. Just like | it must be on
the first column to differentiate with symbol definitions which do have
a leading space on their lines.
Oh, then deb-symbols(5) is wrong for both * and |... oh, I see, I was
misreading
Raphael Hertzog hert...@debian.org writes:
I think this description adapted from the deb-symbols(5) manual page
mislead you into thinking that there were leading spaces before | or *
when in fact there are none.
I have updated the manual page to make it look like this now:
library-soname
Dear Russ and Raphaël,
here are some comments about the current patch. I agree with the other changes
made subsequently in that thread.
+ If a package contains a binary or library which links to a
+ shared library, we must ensure that, when the package is
+ installed on
Charles Plessy ple...@debian.org writes:
here are some comments about the current patch. I agree with the other
changes made subsequently in that thread.
+ If a package contains a binary or library which links to a
+ shared library, we must ensure that, when the package is
+
Russ Allbery r...@debian.org (13/01/2012):
Yes, but there was some discussion in the Policy bug asking why shlibs
files were required when they're not used if a symbols file is present,
and while I originally argued that keeping them both made sense, I came
around to that position after
Cyril Brulebois k...@debian.org writes:
Russ Allbery r...@debian.org (13/01/2012):
Yes, but there was some discussion in the Policy bug asking why shlibs
files were required when they're not used if a symbols file is present,
and while I originally argued that keeping them both made sense, I
11 matches
Mail list logo
