Dne Friday 09 of November 2007 10:51:10 Jiří Suchomel napsal(a):
On čt 1. listopadu 2007, Lukas Ocilka wrote:
Hi, ... These modules use Language YCP module: add-on autoinstallation firstboot installation metapackage network packager
First, I'm definitely not against moving whole Language.ycp or some its part to yast2.rpm (if it is possible - I would prefer not moving the data files).
It could be good that other modules don't need to require yast2-country.
However, don't be so scared by this:
Language.ycp is part of yast2-country which directly uses (requires) these rpms: yast2 yast2-bootloader yast2-storage yast2-x11
is not entirely true:
- functions from yast2-x11 are used only when the package is installed. There's no requirement.
- API of yast2-storage is used only during installation, therefore it is not in the list of requires (but it's probably coded wrongly in timezone/src/dialogs.ycp: the import of Storage should be moved into some client to ensure it is not imported when yast2-storage is not installed)
Looking at the dependency on yast2-bootloader, language.ycp uses only GfxMenu::Update call. AFAICS GfxMenu.ycp doesn't use anything special from yast2-bootloader except the sysconfig agent definitions, so maybe this one (together with cfg_bootloader.scr and cfg_bootsplash.scr) could be moved to yast2.rpm as well?
Well, GfxMenu is there to regenerate the bootloader menu (to contain translations for the new languages). After this is done, the rest depends on the bootloader: In case of GRUB, that's it, in case of LILO it has to call /sbin/lilo. Clean solution would be to make it depend on perl-Bootloader, however, currently it is solved by a hack and /sbin/lilo is called directly. So, yes, this may be an option. 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