summaryrefslogtreecommitdiff
path: root/TODO
diff options
context:
space:
mode:
authorDieter Plaetinck <dieter@plaetinck.be>2008-11-17 18:35:09 +0100
committerDieter Plaetinck <dieter@plaetinck.be>2008-11-17 18:35:09 +0100
commit108af1ce3e6345be48813046b585504d79d99eaf (patch)
treed78f476c86bb2e1d497c7a61fbdc4f45e6c270f5 /TODO
parentaef60a91f36974b2b054cd6f6296615a2553bf4c (diff)
split up the official and unofficial todos
Diffstat (limited to 'TODO')
-rw-r--r--TODO5
1 files changed, 3 insertions, 2 deletions
diff --git a/TODO b/TODO
index b101547..9c64952 100644
--- a/TODO
+++ b/TODO
@@ -30,6 +30,7 @@ not mounted under /mnt
* dieter/automatic: wait for yaourt --config fix
* dieter/automatic: put config files from svn in place first, so that if a package has an update, it can do it's thing.
* on boot after fresh install sometimes filesystem creation date is newer then current date -> fsck. sometimes even forced reboot. (i've had this witch /arch/setup too)
+-> ASKDEV
* /home doesn't get made separately in automatic installer. it's not formatted in sfdisk or _mkfs'd. is this only in virtualbox or elsewhere too?
BETA PHASE: try to get aif on the (beta) installcd as an experimental, alternative installer.
@@ -56,7 +57,7 @@ PRODUCTION PHASE: be the primary installer. deprecate /arch/setup and /arch/qui
SOMEDAY/MAYBE/RANDOM THOUGHTS:
* the quickinst assumes the user did some stuff by himself and does some
after-processing. Would it be useful to have a procedure that always tells
-the user what to do (manually) ?
+the user what to do (manually) ? -> ASKDEV
* profiles like 'desktop','server' (~-> package list, configs, disk setup,..) are crossconcerns
compared to procedures (which are about "how" the installation goes:
prescripted, autodetection, interactive,...).
@@ -68,7 +69,7 @@ whereas for interactive procedures it could provide some other defaults.
* we run mkinitcpio twice: one while installing kernel packages, once after
configuring the system (mkinitcpio.conf). can we optimize this?
* core/interactive -> install packages -> dependency cycles with glibc. not
-a problem?
+a problem? -> ASKDEV
WORRIES FOR MAYBE NO GOOD REASON