Dne Friday 14 of September 2007 13:03:11 Rajko M. napsal(a):
On Friday 14 September 2007 05:02, Klaus Kaempf wrote:
I'd also like to know more about the size of the mentioned problem. Whats the effect on the customer when module compilation is done on-the fly? Whats the effect on the developer ?
From user prospective: Printer module on first start gives message "printer database is changed" (or something similar), than it is doing something for long enough (Athlon 64 3500) to bring question what is changed in database in new installed system? Why database is not created before? If that would be repeated on every module start, than it will be a problem to think how to optimize it.
The problem is that there are several packages holding the drivers, which have to be compiled into one database. That's why there can not be one database which can be used out of the box after installation. Jiri -- Regards, Jiri Srain YaST Team Leader --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain@suse.cz Lihovarska 1060/12 tel: +420 284 028 959 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org