On Thu, 20 Jun 2013 15:14:54 +0200
Klaus Kaempf kkae...@suse.de wrote:
* Josef Reidinger jreidin...@suse.cz [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
* Josef Reidinger jreidin...@suse.cz [Jun 21. 2013 10:40]:
On Thu, 20 Jun 2013 15:14:54 +0200
Klaus Kaempf kkae...@suse.de wrote:
Exactly. Put all the 'knowledge' into SCR and shield SCR users from
this.
And this is where I see problem. Let consider two main use cases for
community
On Fri, Jun 21, 2013 at 10:40:29AM +0200, Josef Reidinger wrote:
On Thu, 20 Jun 2013 15:14:54 +0200
Klaus Kaempf kkae...@suse.de wrote:
* Josef Reidinger jreidin...@suse.cz [Jun 20. 2013 13:37]:
Idea is that installation should drive it.
Agreed.
SCR is implemented in way,
* Arvin Schnell aschn...@suse.de [Jun 21. 2013 10:53]:
And we shouldn't forbid others from what we do ourself, see
libzypp and libstorage. Both don't use SCR.
Both libraries are part of the YaST backend and (hopefully) prevent
developers from calling 'rpm', 'parted' or 'mount' directly.
Hello,
On Jun 21 10:40 Josef Reidinger wrote (excerpt):
It would be nice to have a lot of NIH
modules or simple wrapper around rest of the World libraries. ( for
me the perfect state is when there is configuration libraries from
third party and we only have layer over it in YaST that
On 06/21/2013 11:39 AM, Klaus Kaempf wrote:
* Arvin Schnell aschn...@suse.de [Jun 21. 2013 10:53]:
And we shouldn't forbid others from what we do ourself, see
libzypp and libstorage. Both don't use SCR.
Both libraries are part of the YaST backend and (hopefully) prevent
developers from
On 06/20/2013 03:14 PM, Klaus Kaempf wrote:
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)
...
On 06/21/2013 01:13 PM, Lukas Ocilka wrote:
Totally hackish solution for this:
--- cut ---
code = '$some_fancy_code_in_ruby'
SCR::Execute(
path('.ruby'),
code
)
--- cut ---
Agent .ruby would then eval() the code.
Sounds horrible but it would do the trick :) I'm not sure about proper
On 06/19/2013 07:10 PM, JiříSuchomel wrote:
V Wed, 19 Jun 2013 16:49:46 +0200
Lukas Ocilka lukas.oci...@suse.com napsáno:
Do you have any idea how we could achieve that with the new YaST? I'd
like to have something like:
You could use Gloves, that's ruby-based, with the potential to replace
Hello,
On Jun 19 16:49 Lukas Ocilka wrote (excerpt):
As I've been implementing new module written in Ruby only
(https://github.com/kobliha/yast-services-manager),
I've found out I actually can't use many generic libraries
because they access the system directly omitting SCR.
...
Do you have
On Wed, 19 Jun 2013 16:49:46 +0200
Lukas Ocilka lukas.oci...@suse.com wrote:
Hi,
As I've been implementing new module written in Ruby only
(https://github.com/kobliha/yast-services-manager), I've found out I
actually can't use many generic libraries because they access the
system
* Johannes Meixner jsm...@suse.de [Jun 20. 2013 10:52]:
Regardless how it will be implemented, what you say is basically:
Even after YCP was replaced by Ruby in YaST, arbitrary
contributors cannot just do Ruby programming as usual
to contribute something to YaST.
Exactly. You still
On Thu, 20 Jun 2013 12:51:22 +0200
Klaus Kaempf kkae...@suse.de wrote:
* Johannes Meixner jsm...@suse.de [Jun 20. 2013 10:52]:
Regardless how it will be implemented, what you say is basically:
Even after YCP was replaced by Ruby in YaST, arbitrary
contributors cannot just do Ruby
On Thu, 20 Jun 2013 13:26:05 +0200
Klaus Kaempf kkae...@suse.de wrote:
* Josef Reidinger jreidin...@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
Hello,
On Jun 20 12:51 Klaus Kaempf wrote (excerpt):
* Johannes Meixner jsm...@suse.de [Jun 20. 2013 10:52]:
Regardless how it will be implemented, what you say is basically:
Even after YCP was replaced by Ruby in YaST, arbitrary
contributors cannot just do Ruby programming as usual
* Josef Reidinger jreidin...@suse.cz [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
* Johannes Meixner jsm...@suse.de [Jun 20. 2013 15:04]:
No programmer expects that 'puts' or 'printf' must work
to output a string to a graphical UI.
Good.
And the programmer should have the same attitude when it comes to
changing config files. What is understandable and accepted in terms of
Hi,
As I've been implementing new module written in Ruby only
(https://github.com/kobliha/yast-services-manager), I've found out I
actually can't use many generic libraries because they access the system
directly omitting SCR.
SCR is a layer that basically allows us to read and write
V Wed, 19 Jun 2013 16:49:46 +0200
Lukas Ocilka lukas.oci...@suse.com napsáno:
Do you have any idea how we could achieve that with the new YaST? I'd
like to have something like:
You could use Gloves, that's ruby-based, with the potential to replace
SCR.
Jiri
--
Jiri Suchomel
SUSE LINUX,
19 matches
Mail list logo
