Charles Plessy ple...@debian.org writes:
Le Sun, Jul 08, 2012 at 09:01:47PM -0500, Jonathan Nieder a écrit :
Here's the same patch with the above fixes applied. Sensible?
Thanks for the corrections.
The patch is seconded by me, Russ and Ansgar, and is ready to be applied.
Applied for the
user debian-pol...@packages.debian.org
tags 641153 - patch
usertags 641153 seconded
thanks
Le Sun, Jul 08, 2012 at 09:01:47PM -0500, Jonathan Nieder a écrit :
Here's the same patch with the above fixes applied. Sensible?
Thanks for the corrections.
The patch is seconded by me, Russ and
Hi,
Jakub Wilk wrote:
* Charles Plessy ple...@debian.org, 2011-12-30, 15:39:
+ A ttBuild-Using/tt field must list the corresponding source
+ package for any such binary package incorporated during the build
s/Build-/Built-/
+ The archive software might reject packages
Charles Plessy ple...@debian.org writes:
here is a proposed patch that uses a slimed version of the paragraphs proposed
by Russ (quoted below) and keeps the original examples.
Looks good to me; seconded as well and thanks for your work.
I agree with Russ that a binary/binary relationship may
Dear all,
here is a proposed patch that uses a slimed version of the paragraphs proposed
by Russ (quoted below) and keeps the original examples. It documents the field
as new section, number 7.8, the last one of its chapter, because it introduces
a new type of relationship, from binary package
* Charles Plessy ple...@debian.org, 2011-12-30, 15:39:
+ A ttBuild-Using/tt field must list the corresponding source
+ package for any such binary package incorporated during the build
s/Build-/Built-/
+ The archive software might reject packages that refer to
+
Hi,
Russ Allbery r...@debian.org writes:
Ansgar Burchardt ans...@debian.org writes:
A try at this:
Some binary packages incorporate material derived from source
or compiled code derived from other source packages. In this case
this field must be used to list all other source packages
Ansgar Burchardt ans...@debian.org writes:
I think source packages better reflect the meaning of the field (keep
the source available). Listing them will hopefully soon no longer be
more complicated than binary package, see [1].
[1] http://bugs.debian.org/653575
In addition listing
Charles Plessy ple...@debian.org writes:
here is a proposed patch that uses a slimed version of the paragraphs
proposed by Russ (quoted below) and keeps the original examples. It
documents the field as new section, number 7.8, the last one of its
chapter, because it introduces a new type of
One basic question about this before I dive into wording: why is the
Build-Depends field not adequate?
Ansgar Burchardt ans...@debian.org writes:
A try at this:
Some binary packages incorporate material derived from source
or compiled code derived from other source packages. In this
Russ Allbery r...@debian.org writes:
One basic question about this before I dive into wording: why is the
Build-Depends field not adequate?
Never mind this question; I figured it out but forgot to remove this part
of my mail.
--
Russ Allbery (r...@debian.org)
Hi,
thanks for your comment and sorry for the late reply, I forgot about
this bug for a while.
Am 11.09.2011 04:38, schrieb Charles Plessy:
thanks for documenting Built-Using in the Policy. I have a couple of
comments about your patch.
@@ -3061,7 +3061,8 @@ Package: libc6
* Ansgar Burchardt ans...@debian.org, 2011-12-12, 14:44:
Also, §7.1 specifies differently the architecture restrictions for
build relationship fields (Build-Depends, Build-Depends-Indep,
Build-Conflicts and Build-Conflicts-Indep) and binary relationship
fields. According to what is expected
Am 12.12.2011 15:14, schrieb Jakub Wilk:
* Ansgar Burchardt ans...@debian.org, 2011-12-12, 14:44:
Also, §7.1 specifies differently the architecture restrictions for
build relationship fields (Build-Depends, Build-Depends-Indep,
Build-Conflicts and Build-Conflicts-Indep) and binary relationship
user debian-pol...@lists.debian.org
usertags 641153 + normative discussion
thanks
Le Sun, Sep 11, 2011 at 11:38:05AM +0900, Charles Plessy a écrit :
Le Sat, Sep 10, 2011 at 10:44:49PM +0200, Ansgar Burchardt a écrit :
some months ago support for the Built-Using field was added to the
On Sun, 11 Sep 2011, Charles Plessy wrote:
This adds Built-Using in §5.6.10 (“Package interrelationship fields: Depends,
Pre-Depends, Recommends, Suggests, Breaks, Conflicts, Provides, Replaces,
Enhances”). In Policy's chapter 5, the fields in that list are documented to
be present in source
Le Sun, Sep 11, 2011 at 08:32:33AM +0200, Raphael Hertzog a écrit :
On Sun, 11 Sep 2011, Charles Plessy wrote:
This adds Built-Using in §5.6.10 (“Package interrelationship fields:
Depends,
Pre-Depends, Recommends, Suggests, Breaks, Conflicts, Provides, Replaces,
Enhances”). In Policy's
Package: debian-policy
Severity: normal
Hi,
some months ago support for the Built-Using field was added to the
archive software. It is used by binary packages to refer to additional
source packages that were used during the build and need to stay in the
archive to have the full source
Le Sat, Sep 10, 2011 at 10:44:49PM +0200, Ansgar Burchardt a écrit :
some months ago support for the Built-Using field was added to the
archive software. It is used by binary packages to refer to additional
source packages that were used during the build and need to stay in the
archive to
19 matches
Mail list logo
