Package: debian-policy
Version: 3.8.1.0
Severity: wishlist
Tags: patch
Hi!
Recommend using the DEB_*_ARCH_CPU and DEB_*_ARCH_OS variables instead
of the GNU style ones. And mention that the latter are mostly intended
for use with upstream build systems, and not Debian packaging.
regards,
guillem
---
policy.sgml | 12 ++++++++++--
1 files changed, 10 insertions(+), 2 deletions(-)
diff --git a/policy.sgml b/policy.sgml
index 144cbfb..b42afe9 100644
--- a/policy.sgml
+++ b/policy.sgml
@@ -1986,6 +1986,12 @@
<tt>DEB_*_ARCH</tt> (the Debian architecture)
</item>
<item>
+ <tt>DEB_*_ARCH_CPU</tt> (the Debian CPU name)
+ </item>
+ <item>
+ <tt>DEB_*_ARCH_OS</tt> (the Debian System name)
+ </item>
+ <item>
<tt>DEB_*_GNU_TYPE</tt> (the GNU style architecture
specification string)
</item>
@@ -2013,8 +2019,10 @@
It is important to understand that the <tt>DEB_*_ARCH</tt>
string only determines which Debian architecture we are
building on or for. It should not be used to get the CPU
- or system information; the GNU style variables should be
- used for that.
+ or system information; the <tt>DEB_*_ARCH_CPU</tt> and
+ <tt>DEB_*_ARCH_OS</tt> variables should be used for that.
+ GNU style variables should generally only be used with upstream
+ build systems.
</p>
<sect1 id="debianrules-options">
--
1.6.3
--
To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
