Hello, In AL5 there's an ambiguity of "build target": which can be the target to build the .deb or to run make (see fakeroot debian/rules build). This patch is an attempt to fix the ambiguity. Ciao, Enrico -- GPG key: 4096R/E7AD5568 2009-05-08 Enrico Zini <enrico@enricozini.org>
From 819c803c63a2fdfa0c3e3f8940cb5cddbd65f4cc Mon Sep 17 00:00:00 2001
From: Enrico Zini <enrico@enricozini.org>
Date: Tue, 11 Aug 2009 15:27:19 +0100
Subject: [PATCH 219/219] Fixed ambiguity about 'build target'
---
nm_ts2.txt | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/nm_ts2.txt b/nm_ts2.txt
index 4308a51..5e07067 100644
--- a/nm_ts2.txt
+++ b/nm_ts2.txt
@@ -50,9 +50,9 @@ AL4. Tell me the differences between /usr/share and /usr/lib.
What would you do if you had a package which includes a mix of
architecture-dependent and architecture-independent files?
-AL5. What build target would you use in debian/rules to build a package
- which includes only non-architecture-dependent files? What is the
- "Architecture:" field for this package?
+AL5. What target in debian/rules would you use in debian/rules to build a
+ .deb package which includes only non-architecture-dependent files?
+ What is the "Architecture:" field for this package?
AL6. What is endianness and why does it matter when supporting multiple
architectures?
--
1.6.3.3
Attachment:
signature.asc
Description: Digital signature