Emilio Pozuelo Monfort po...@ubuntu.com writes:
Greetings from this new -policy subscriber!
Russ Allbery wrote:
@@ -4188,6 +4188,22 @@ Build-Depends-Indep: texinfo
Build-Depends: kernel-headers-2.2.10 [!hurd-i386],
hurd-dev [hurd-i386], gnumach-dev [hurd-i386]
/example
+
Don Armstrong d...@debian.org writes:
On Sun, 25 Jan 2009, Russ Allbery wrote:
+ If the architecture-restricted dependency is part of a set of
+ alternatives using tt|/tt, that branch of the alternative is
+ ignored completely on architectures that do not match the
+
Hi!
On Sun, 2009-01-25 at 15:20:02 -0800, Russ Allbery wrote:
I finally found some time to write new proposed wording for the section in
Policy on handling architecture-restricted dependencies. Could you review
this change and be sure that I'm correctly describing the situation? I
added a
Greetings from this new -policy subscriber!
Russ Allbery wrote:
@@ -4188,6 +4188,22 @@ Build-Depends-Indep: texinfo
Build-Depends: kernel-headers-2.2.10 [!hurd-i386],
hurd-dev [hurd-i386], gnumach-dev [hurd-i386]
/example
+ requires ttkernel-headers-2.2.0/tt on all
On Sun, 25 Jan 2009, Russ Allbery wrote:
+ If the architecture-restricted dependency is part of a set of
+ alternatives using tt|/tt, that branch of the alternative is
+ ignored completely on architectures that do not match the
+ restriction. For example:
+
I finally found some time to write new proposed wording for the section in
Policy on handling architecture-restricted dependencies. Could you review
this change and be sure that I'm correctly describing the situation? I
added a new, fairly complicated example based on one of the ones that
dpkg folks,
Bug#163666 against debian-policy points out that arch-specific build
dependencies are unclearly specified in Policy currently in the presence
of alternatives. The current wording says:
All fields that specify build-time relationships (`Build-Depends',
Hi,
On Sat, 2008-07-05 at 17:09:48 -0700, Russ Allbery wrote:
Bug#163666 against debian-policy points out that arch-specific build
dependencies are unclearly specified in Policy currently in the presence
of alternatives. The current wording says:
All fields that specify build-time
8 matches
Mail list logo