2007/4/16, DongInn Kim <[EMAIL PROTECTED]>: > > Why should we re-invent the wheel ? In the config.xml file, we have a whole > > bunch of tags to describe package dependancies. If config.xml schema does > > not > > handle your problem, it can be updated. > > > Jean, good point. But we have not written a code to handle the prereq > configuration in packages/*/config.xml and we have never put the prereq > configuration in config.xml. So would you re-write whole codes to take > care of prereqs by putting all the other prereqs to config.xml and then > write/call another code to parse the config.xml to use the prereq config > at the proper point? Looks like this is more work for me. If I am > missing your point, please correct me. > Anyways, nonetheless if having the prereqs in config.xml is a right > thing to do for the future, I think we have to consider doing it this way.
This is a "chicken or egg" problem. Before config.xml can be parsed one needs to get the prereqs installed. The prereqs enable the system to parse config.xml files. So the prereqs must run allways and have no requirements like XML parser and so on. prereq.cfg also contains instructions to delete certain packages, as well as invoke particular external scripts. Don't know if anybody remembers the mess before prereq.cfg, that's not so long ago, BTW. Regards, Erich ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
