Some of you may know by now, since January SUSE developers in Prague are working on automatically translating the YaST codebase from YCP (an old proprietary language) into Ruby.
We could see this in openSUSE 13.1 Milestone 4. See this [yast-devel] Integration of YaST in Ruby into Factory/openSUSE 13.1](http://lists.opensuse.org/yast-devel/2013-05/msg00035.html)
Another interesting link [yast-devel] YCP Killer: Installer is working](http://lists.opensuse.org/yast-devel/2013-05/msg00026.html)
So 13.1 will feature “new” YaST ? They should called Reborn-YaST
YaSTR… yast-Reborned … yast-Ruby…
but there will be new features or will be yast only translated ??
ciao pier
On 05/31/2013 12:06 PM, pier andreit wrote:
>
> vazhavandan;2561692 Wrote:
>> So 13.1 will feature “new” YaST ? They should called Reborn-YaSTYaSTR… yast-Reborned … yast-Ruby…
> but there will be new features or will be yast only translated ??
> ciao pier
From the various links it looks like this is just translation, but new
features will come as they always do separately.
One feature I cannot find in there is compatibility with YCP modules going
forward. Will they still work for a while? I ask because I know of some
third-party modules used for appliance installers which will need to,
eventually, be ported to Ruby.
Thanks everybody for the update; this is a nice move to allow people to
get more-involved by using a more-common language.
Good luck.
Good question . It would be bad if it is a hard switch over. YaST modules have been around for Eons and some might even be using custom ycp modules
I don’t know as to why they are even switching to “new” system as ycp looking simple scripting language.
// Hello, World in YCP
{
UI::OpenDialog(
`VBox(
`Label("Hello, World!"),
`PushButton("OK")
)
);
UI::UserInput();
UI::CloseDialog();
}
How abour RYaST.
I switched to yast head and now yast runs slower than a zilog z80 8 bit running sinclairs basic. in short it needs a lot of work by ms 4
you can say that again. When i switched back yast2 felt like Ferrari.
RubyYaST is nowhere a YCP killer as of now 
optimize performance and memory usage of Ruby code if this proves necessary.
source:- [yast-devel] Integration of YaST in Ruby into Factory/openSUSE 13.1](http://lists.opensuse.org/yast-devel/2013-05/msg00035.html)
Guess, It is not an optional step anymore.
Did you discuss this on yast-devel mailing list?
i will wait for 13.1 milestone(M4: 2013-08-08) and check whether performance improves
On 2013-06-01 03:36, vazhavandan wrote:
> I don’t know as to why they are even switching to “new” system as ycp
> looking simple scripting language.
Because YCP is a proprietary language (they could open it, though). The problem is that there are
few developers for it, and new ones need to learn the language first. They think that using a
mainstream scripting language may increase the number of contributors.
–
Cheers / Saludos,
Carlos E. R.
(from oS 12.3 “Dartmouth” GM (rescate 1))
Will SLED/SLES also migrate to ruby ?
On 06/03/2013 06:36 AM, vazhavandan wrote:
> Will SLED/SLES also migrate to ruby ?
probably need to ask the SLED/SLES folks…not a lot of those
read/answer around here…
–
dd
It would be Yast Inc(arnated).
On 2013-06-03 06:36, vazhavandan wrote:
> Will SLED/SLES also migrate to ruby ?
Of course, but after we pave the way, breaking our transmission in the process. >;-)
–
Cheers / Saludos,
Carlos E. R.
(from oS 12.3 “Dartmouth” GM (rescate 1))
On 06/03/2013 01:00 PM, Carlos E. R. wrote:
> breaking our transmission in the process
that is one of the ‘cost’ paid by the users of a community upstream
of commercial organization who is the prime ‘sponsor’ of community
activities…
alternatives are plenty:
pay for the associated commercial operating system
pay for any other commercial operating system
find a non-commercial competing product with less ‘costs’ (like
breaking the toy every 8 months)
switch to 11.4 Evergreen and HOPE 13.1 comes in both unbroken and
planned to slide into Evergreen also…
the choice IS in the hands of the user (aka community release
testers)–and, if there are no users/testers there will be no more
breakage…because the train will stop.
–
dd
and to listen the rants and kids of the tester is one of the costs of a commercial organization …:)
Follow Up
Looks there are some developments on the Factory mail list. Presently Ruby 1.8 is being used. It will speed up with Ruby 1.9.
Benchmarks Ruby 2.0
Excerpt from Josef Reidinger’s email:
“So my hope is that we just replace one dependency by another.
But to be honest to you, it won’t happen in 13.1 as there is still small parts
that use ycp code as data format and we kept it there to not break
anything. Plan is to remove it in next steps.”
For something major as Yast, I believe it is too soon for Ruby Yast to be introduced in 13.1
+1 Facebook Like
On 2013-06-03 20:16, pier andreit wrote:
>
> DenverD;2562262 Wrote:
>> On 06/03/2013 01:00 PM, Carlos E. R. wrote:
>>> breaking our transmission in the process
>>
>> that is one of the ‘cost’ paid by the users of a community upstream
>> of commercial organization who is the prime ‘sponsor’ of community
>> activities…
> and to listen the rants and kids of the tester is one of the costs of a
> commercial organization …:)
Absolutely!
And they don’t do that much nowdays.
–
Cheers / Saludos,
Carlos E. R.
(from oS 12.3 “Dartmouth” GM (rescate 1))