Hi folks, as you might have seen more and more FSO 2.0 subsystems are ready for prime time, so we have to think about how configuration works for FSO 2.0. Until now I used the same method as in FSO 1.0, which is having it lumped all together in one config file. For FSO 2.0 I'm leaning towards changing this. The benefit I see from one configuration file per subsystem is:
*) promoting the fine granular usage of individual FSO subsystems, *) enable packagers to ship the config with the subsystem, if they want, *) a third reason which i forgot while writing this mail. What do you think? -- :M: _______________________________________________ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
