From 6bde469372047d50ff67b7bd56ecd87b831f38bf Mon Sep 17 00:00:00 2001
From: P. J. McDermott <pj@pehjota.net>
Date: Mon, 18 Aug 2014 19:54:17 -0400
Subject: notes.txt: Drop old information

---
(limited to 'notes.txt')

diff --git a/notes.txt b/notes.txt
index 7e2f041..03337fc 100644
--- a/notes.txt
+++ b/notes.txt
@@ -1,6 +1,3 @@
-host arch is determined at build time
-
-
 prokit install [-a <arch>] [-P <plat>] <suite> <chroot>
 	<suite>
 		e.g. rs1, dev/trunk, or proteanos:dev/trunk
@@ -24,52 +21,6 @@ buildd:
     host$ prokit opkbuild chroot chroot/usr/src/expat_*/
 
 
-TODO:
-
-profiles, e.g. proteanos
-each profile has its own tests for host arch/plat
-also, how does debootstrap determine host arch on non-Debian hosts?
-	apparently it doesn't
-	(must pass --arch, then debootstrap can't detect if host != target)
-
-configure
-	--with-profile=proteanos
-	--with-arch=core-linux-eglibc
-	--with-plat=dev
-
-profiles/
-  +- proteanos
-      +- archtab
-      +- plattab
-      +- feedtab
-
-should profiles be left to run time?
-Debian/etc. packaging: proinst-proteanos? proinst with all profiles? arch:any?
-
-m4_include profiles/profiles.m4
-PI_PROFILE
-
-configure
-	--with-proteanos-arch
-
-maybe better: at run time:
-	look in sysconfdir for host arch value
-		in-place: etc/proinst_arch?
-		distributions can make this file in postinst
-	otherwise, autodetect
-
-or just autodetect and "cache":
-	`prokit install` detects host arch
-		profile-specific config.guess-like function
-	`prokit shell` and `prokit opkg` look for /inst
-		add /inst to PATH and run /inst/bin/sh and /inst/usr/bin/opkg
-	`prokit build` looks for /inst
-		screams something about "unsupported" and "cross install"
-		then bails
-		if no /inst, opkbuild
-		opkbuild will find /etc/proteanos_{arch,plat} and do magics
-
-
 run_cmd()
 {
 	if $# lt cmd_$cmd_min_args
--
cgit v0.9.1