* Josef Reidinger <jreidinger@suse.cz> [Jun 20. 2013 13:22]:
One idea that I use in gloves is run code in chroot. Problem is that it means, you need already system with code installed. But for me it is also valid approach something like
make_proposals install_jeos chroot("/mnt") do write_configuration end
But I also agree that it is quite big change.
Well, chroot() is fine if it's called once, when the backend is initialized. A normal YaST module shouldn't even be aware to which file the backend writes. Klaus -- SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5, 90409 Nürnberg, Germany -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org