Mailinglist Archive: yast-devel (66 mails)

< Previous Next >
Re: [yast-devel] Ruby code in SCR
* Josef Reidinger <jreidinger@xxxxxxx> [Jun 20. 2013 13:37]:

Idea is that installation should drive it.

Agreed.

SCR is implemented in way,
that you must use SCR and SCR must be aware where it runs, so it is
done on low level.

Exactly. Put all the 'knowledge' into SCR and shield SCR users from
this.


My idea is that installation should drive it and top level module
should do something like chroot.run TopLevel::Method...like chroot.run
Network.write (complex_map)

This seems to add lots of complexity (and responsability) to
individual modules.

Instead of

chroot.run Network.write(complex_map)

I'd rather see something like

# global 'chroot' call, done by installer
SCR.init("/mnt")
...
Network.write(complex_map)

and

module Network

# SCR init still needed if Network is run stand-alone
# it's a no-op if SCR.init was called before
SCR.init
...
SCR.write ...
end

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@xxxxxxxxxxxx
To contact the owner, e-mail: yast-devel+owner@xxxxxxxxxxxx

< Previous Next >