Good News
The following was copied from an email from David Majda on the Factory ML.
<---------------- snip
We are proud to announce that we just reached the main goal of the YCP Killer project: we did the final conversion of YaST codebase from YCP to Ruby and integrated the result into Factory
(which means YaST in Ruby will be part of openSUSE 13.1 M4). At the same time, YaST version was officially increased to 3.0.0.
This concludes 6 months of effort and opens many new possibilities for further YaST development.
The translation itself was done automatically using Y2R – a YCP to Ruby transpiler. The amount of converted code is quite impressive:
- 4204 files
- 594680 lines of YCP deleted
- 724687 lines of Ruby added
The change of the implementation language should not bring any noticeable change in the appearance or behavior of YaST or the openSUSE installer. If you spot any difference, it is a bug and please report it via regular channels (primarily Bugzilla). At this point we are not aware of any user-visible problems.
Thanks to everybody who participated on this huge effort."
[1] https://github.com/yast/ycp-killer
[2] https://github.com/yast/y2r
<---------------- snip
Now,the big job will be to catch as many bugs in Milestone 4 as possible. We would like to make Yast as stable as possible before openSUSE 13.1 is released.
Romanator wrote:
> Bugzilla). At
Great news indeed. Keeping my fingers crossed that YaST installer works
without a hitch when 13.1 comes out
–
GNOME 3.6.2
openSUSE Release 12.3 (Dartmouth) 64-bit
Kernel Linux 3.7.10-1.16-desktop
Oh yeah. We have to really stay on top of any bugs that we may encounter as Yast is somewhat of a centrepiece with openSUSE 13.1.
I think this potentially might be a good move because it will encourage yast to move forward faster! 
Yes, it sets the stage for further evolvement now which is a significant asset for openSUSE.
On 2013-08-02 22:16, Romanator wrote:
>
> Oh yeah. We have to really stay on top of any bugs that we may encounter
> as Yast is somewhat of a centrepiece with openSUSE 13.1.
Translation is broken.
On some strings “/n” has been replaced with “//n”, and also translating
comments are missing.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
Please report.
On some strings “/n” has been replaced with “//n”, and also translating
comments are missing.
David had mentioned that there are bugs in the transpiler. He followed up with the following:
The conversion is final.
If we find a significant bug in the converter now, our plan is:
- Fix the converter.
- Re-run the conversion on the snapshot of YaST code we did before
the official final conversion.
- Take a diff against the original converted code.
- Apply that diff on current YaST code (as a regular patch).
Of course, this will be possible only for some time, because YaST code will evolve. But this is OK.
BTW we tested a lot, so we expect the number of bugs to be low.
Now we need them to get it to run faster and more responsive.
On 2013-08-03 21:56, Romanator wrote:
>
> robin_listas;2576633 Wrote:
>> On 2013-08-02 22:16, Romanator wrote:
>>>
>>> Oh yeah. We have to really stay on top of any bugs that we may
>> encounter
>>> as Yast is somewhat of a centrepiece with openSUSE 13.1.
>>
>> Translation is broken.
>
> Please report.
It was already reported by somebody else, I’m just commenting.
Original comment was in translation mail list and yast mail list:
On 08/02/2013 08:36 AM, Ladislav Slezak wrote:
> This was caused by switching from YCP to Ruby which needs
> using Ruby gettext (rxgettext) instead of GNU gettext (xgettext).
>
> For me it looks like a bug, I’ll investigate further.
>
> Moreover many comments are missing, this is another incompatibility
> in rxgettext and needs to be solved.
>
>
> For now ignore the new translations, and I think the last changes
> could be even reverted to not cause confusions for translators…
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
I’m still concerned about the Yast Extended Partition Editor. I ran into a number of crashes when deleting a partition and resizing existing partitions.
We’ll see in Milestone 4.