summaryrefslogtreecommitdiff
path: root/TODO
blob: 572a289668af21c6e411180e690ff0d29907ddb1 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
* each profile can have libs for
- ui (most stuff goes into lib-ui however, only very specific custom things
  not)
- backend (eg dieters automatic stuff is custom for dieter. but can have
different installation procedures using the same custom backend code)
- implementation (what a profile is right now) -> rename profile to
procedure
* the above requires now file layout: all 'core' things must be separate
from user things
- core: all stuff that should be on install cd for all users
- user: specific libs (whether ui, backend,...) and procedures.
* it should also be possible that one user creates multiple procedures, using
the same - custom - libraries, (a very basic dependency check? eg need
lib_dieter, which checks user/lib/lib-dieter)
* base profile wordt implementatie van alles wat auto gaat uit setup script,
other steps warning 'not implemented'
* in automatic-dieter: health check using svn info /<hostname> 
* in elke phase een lege worker die te overriden valt zoda we geen phases
  moeten overriden
* process and fix libraries
* fix to use $var_UI_TYPE where needed
* write the ui functions for asking questions etc for both cli and dialog and port all code to use it. 
* instead of using the 'base' profile and letting other profiles override,
  we should have even more flexibilty to take parts from different profiles.
  eg dieter profile maybe wants to use something interactive. or base
  profile wants to do something interactive. interactive functions maybe
  dont belong in a profile?

* base profile idea: it should just tell you what to do? -> less
  implementation work in base profile, more in other profiles...
* fix crossconcerns: some procedures could be about _what_ (desktop,server),
  others are about _how_ (autodetection, asking user,...) (profile vs...
  'mode' ?)
* port classic installer so it works with fifa
* make some sensible default profiles (eg desktop, server, ...)
* make it work
* someday.. make a script '/arch/setup' that calls '/arch/fifa.sh interactive'