From 441368eafe8f67f444a859d0de12c0bea31e2124 Mon Sep 17 00:00:00 2001
From: DJ Delorie <dj@delorie.com>
Date: Wed, 15 Jun 2011 22:51:08 -0400
Subject: Clarify handling of build order and can't-build packages

---
 stage2 | 16 ++++++++++++----
 1 file changed, 12 insertions(+), 4 deletions(-)

diff --git a/stage2 b/stage2
index 9e5a17d..622e87a 100755
--- a/stage2
+++ b/stage2
@@ -134,6 +134,9 @@ case "$1" in
     "" )
 	go clean
 
+	# Keep these in the order in which they must be built.  You
+	# will thus normally add new packages to the end of the list.
+
 	go cpio
 	go ncurses
 	go m4
@@ -144,14 +147,12 @@ case "$1" in
 
 	go curl
 	go nspr
-	go rpm	# not yet
-        go pcre
-        go readline
+	go pcre
+	go readline
 
 	go chkconfig
 	go sqlite
 	go gdbm
-	go gnupg # not yet
 	go gawk
 	go pth
 	go libtool
@@ -164,11 +165,18 @@ case "$1" in
 	go pkgconfig
 	go nss
 
+	# Packages known to not build yet - should be a clause later
+	# in the file describing why.
+
+	# go gnupg	# not yet
+	# go rpm	# not yet
 	;;
 
     "clean" )
 	;;
 
+    # Packages built by stage1
+
     binutils | gcc | glibc | kernel | x-loader | u-boot \
     | gmp | mpfr | mpc | ppl | cloog | libselinux | zlib \
     | bash | make | sed | coreutils | util-linux | tar | gzip \
-- 
cgit