Julien Cristau jcris...@debian.org writes:
On Sun, Aug 12, 2012 at 14:25:12 -0700, Russ Allbery wrote:
Okay, once more for the win. Here is the current version of the patch,
incorporating substantial improvements from Jonathan Nieder and
hopefully incorporating all the feedback in subsequent
On Sun, Aug 12, 2012 at 14:25:12 -0700, Russ Allbery wrote:
Okay, once more for the win. Here is the current version of the patch,
incorporating substantial improvements from Jonathan Nieder and hopefully
incorporating all the feedback in subsequent discussion.
I'm looking for seconds so
Hi,
On Sun, 12 Aug 2012, Russ Allbery wrote:
I'm looking for seconds so that we can finally merge this monster.
Presented as a diff since that was the request last time, but the branch
has also been pushed to the Policy Git repository, so if you want to
review it various other ways, you can
Jonathan Nieder jrnie...@gmail.com writes:
Jonathan Nieder wrote:
I'll reply with an interdiff relative to the last version of the
patch.
Here it is.
And here is the interdiff between your patch and what I currently have, to
make it easier for you and anyone who was familiar with your
Russ Allbery r...@debian.org writes:
commit 97cb027db4afab774ea4f4ff9e7bef7a6dcbbda0
Author: Russ Allbery r...@debian.org
Date: Sun Aug 12 14:14:23 2012 -0700
Further wording changes on top of Jonathan Neider's work
I fixed the spelling of your name in Git before I pushed. Sorry
* Russ Allbery r...@debian.org [120317 19:17]:
These two mechanisms differ in the degree of detail that they
provide. A filesymbols/file file documents every symbol
that is part of the library ABI and, for each, the version of
the package in which it was
On Mon, Mar 19, 2012 at 17:26:04 -0500, Jonathan Nieder wrote:
These dependencies must be added to the binary
package when it is built, since they may change
This means packages must not hard-code library dependencies. It
also seems like good policy, but I
Le Sat, Mar 17, 2012 at 11:17:29AM -0700, Russ Allbery a écrit :
Here is a new proposed patch that incorporates the feedback to date with
some other, substantial changes.
Due to the reformatting, the diff is even longer and is now really just
the complete removal of the current shlibs section
Here is a new proposed patch that incorporates the feedback to date with
some other, substantial changes.
It's apparent to me from hands-on experimentation with C++ libraries that,
at least at the moment, shlibs is likely to have an ongoing existence in
the archive. Accordingly, some of the
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
Hi,
On Mon, 02 Jan 2012, Russ Allbery wrote:
p
If a package contains a binary or library which links to a
shared library, we must ensure that, when the package is
installed on the system, all of the libraries needed are also
installed. These
* Russ Allbery r...@debian.org, 2012-01-02, 13:51:
p
A common example of when a change
to varminimal-version/var is required is a function that
takes an enum or struct argument that controls what the
function does. For example:
Hello folks,
I took some time today and wrote a first draft of a new section of Policy
documenting symbols files, and the revisions to shlibs for their
interaction. Please review. There's quite a lot of material here,
including details from dpkg-shlibdeps, dpkg-gensymbols, and deb-symbols
22 matches
Mail list logo
