summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTWikiGuest <web-hurd@gnu.org>2005-07-28 04:11:31 +0000
committerTWikiGuest <web-hurd@gnu.org>2005-07-28 04:11:31 +0000
commite75ac37c3ef90a440cf018a76e092c2bff7e0023 (patch)
tree881fbefefa6d2e8e13e61d1221a28f20e074f575
parent8506cc481d7866e97a2eec4de25bd5666630e1db (diff)
none
-rw-r--r--Distrib/GnuOS.mdwn9
1 files changed, 9 insertions, 0 deletions
diff --git a/Distrib/GnuOS.mdwn b/Distrib/GnuOS.mdwn
index 09b697d5..5764a2c6 100644
--- a/Distrib/GnuOS.mdwn
+++ b/Distrib/GnuOS.mdwn
@@ -50,3 +50,12 @@ These are just some quick notes I am making late at night. Lets clean this up.
* Native installer would be preferred but we can bootstrap GNU/Linux for now if necessary
3. Package Management
* There is a proposal to use stowfs. Let's get this going and test it out. Can it be made to work? How long will it take?
+
+## <a name="Moving_forward_"> Moving forward? </a>
+
+1. AMS had made a GNU release. We can try it and test it to good use. We can fix broken things in it, and enhance it.
+2. GNU is all about freedom AND ease of use. So, given installers are by nature quite complex, how should we install GNU on users's computers? I think ams's GNU System Creator comes into play here, maybe ams or sdschulze could (re-)write specifications of GSC.
+3. Until we have an installer ready, we could go the Gentoo-like route, and have every part manually installed. A good installation documentation may help. Our next milestone may be just this (in case ams hasn't already done it):
+ * have a good installation document out, with all the required packages hosted at gnu.org or savannah.org
+ * get stowfs working
+4. Move on, start coding, documenting, packaging.