Le jeudi 28 septembre 2006 12:57, Erich Focht a écrit : > IMO you should at least print some warning in the case that the check > was not actually done because the package is missing. I just checked, you > do print a warning, so... well... should I add
I am already printing a warning, but FYI because the core team rejected the idea of warnings in the system-sanity mechanism, it is just a message to the user, the system itself is not notified (which is fine for me). > sh: $OSCAR_HOME/scripts/system-sanity.d/ssh-check.pl > to the prereq.cfg? Or repeat the whole sanity check? Or not do it at all? I really do not know. I started to work a while ago on a Sanity Check framework but part of the core team was pretty opposed to such a mechanism so i have to admit i gave up the idea and therefore i do not know today how to deal with sanity check during system execution. If at the end such a mechanism is considered as valuable, i will try to spend some time of the subject later, unfortunately, i do not have the time for that right now. Regards, -- Geoffroy ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
