[yast-devel] YaST Ruby final conversion & integration - DONE
Hi, we are pleased to announce that the final Ruby conversion of YaST YCP code to Ruby is over. The converted source was committed to Git [1], passed through Jenkins and builds successfully in YaST:Head [2]. YaST version was increased to 3.0.0. We also sent submit requests to Factory (not accepted yet). ** YaST Git repositories are open for development again. ** Thanks everybody for patience and welcome to the new Ruby era :-) Technical Details ----------------- In all affected Git repositories, we used the following Git tags to mark the conversion: * good-bye-ycp -- last commit before the conversion * hello-ruby -- last commit of the conversion You can use them to see the changes the conversion did, e.g.: https://github.com/yast/yast-yast2/compare/good-bye-ycp...hello-ruby The amount of converted code is quite impressive: * 4204 files * 594680 lines of YCP deleted * 724687 lines of Ruby added Issues ------ There are few small issues that remain to be solved: * There were problems running tests on Jenkins for several packages. We solved them temporarily by fiddling with the test scripts, but we need to fix them more properly. Josef & Martin will look into that. Note the tests still pass correctly in when building in the OBS. * Module "iplb" is currently broken -- it wasn't converted, but its tests don't work after converting "testsuite" into Ruby. We need to clarify status of this module and fix it or drop it. Next Steps ---------- In the coming days and weeks, we would like to do the following: 1. Publish a document describing what the conversion changed (and how) and what remained the same. This will make starting with Ruby YaST easier for everybody who was not involved in the conversion. 2. Publish a document describing how to best handle YaST maintenance fixes in the old YCP code base which will need to be applied back to Ruby. 3. Decide on how exactly to do documentation and testing. 4. Update the skeleton that shows how to create a new YaST module to Ruby and describe the best practices. 5. Initiate a discussion about further changes and improvements in YaST architecture, which would allow us simplify it even more and make YaST even more attractive to contributors. [1] https://github.com/yast/ [2] https://build.opensuse.org/project/show/YaST:Head -- David Majda SUSE Studio developer http://susestudio.com/ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On Wed, Jul 31, 2013 at 03:42:04PM +0200, David Majda wrote:
we are pleased to announce that the final Ruby conversion of YaST YCP code to Ruby is over. The converted source was committed to Git [1], passed through Jenkins and builds successfully in YaST:Head [2].
Could you please reenable openSUSE 12.3 in YaST:Head so that we can install the great new packages on our systems? Or what is the best way to start development? ciao Arvin -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Dne 31.7.2013 15:48, Arvin Schnell napsal(a):
On Wed, Jul 31, 2013 at 03:42:04PM +0200, David Majda wrote:
we are pleased to announce that the final Ruby conversion of YaST YCP code to Ruby is over. The converted source was committed to Git [1], passed through Jenkins and builds successfully in YaST:Head [2].
Could you please reenable openSUSE 12.3 in YaST:Head so that we can install the great new packages on our systems? Or what is the best way to start development?
Yes, I have reenabled it again, you just need to wait until the rebuild is finished. You need updated core, all *-bindings, devtools and others. The best way is to run zypper ar -f http://download.opensuse.org/repositories/YaST:/Head/openSUSE_12.3/ YaST:Head zypper dup --from YaST:Head Enjoy! -- Ladislav Slezák Appliance department / YaST Developer Lihovarská 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak@suse.com SUSE -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 07/31/2013 03:42 PM, David Majda wrote:
Hi,
we are pleased to announce that the final Ruby conversion of YaST YCP code to Ruby is over. The converted source was committed to Git [1], passed through Jenkins and builds successfully in YaST:Head [2]. YaST version was increased to 3.0.0. We also sent submit requests to Factory (not accepted yet).
Thanks to the team for all this awesome job! Well done! :) Now it's time to think about what we want to do next, what are the next pain-points we want to solve - but this has to be discussed with all the team members together. Bye Lukas -- Lukas Ocilka, Cloud & Systems Management Department SUSE LINUX s.r.o., Praha -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 07/31/2013 04:28 PM, Lukas Ocilka wrote:
On 07/31/2013 03:42 PM, David Majda wrote:
Hi,
we are pleased to announce that the final Ruby conversion of YaST YCP code to Ruby is over. The converted source was committed to Git [1], passed through Jenkins and builds successfully in YaST:Head [2]. YaST version was increased to 3.0.0. We also sent submit requests to Factory (not accepted yet).
Thanks to the team for all this awesome job! Well done! :) Congratulations, ycp killers!
Now it's time to think about what we want to do next, what are the next pain-points we want to solve - but this has to be discussed with all the team members together.
Are ycp-ui-bindings still used? Are they going to be replaced by ruby-ui-bindings? Cheers, Thomas
Bye Lukas
-- Thomas Goettlicher 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
On Thu, 01 Aug 2013 11:11:29 +0200
Thomas Goettlicher
On 07/31/2013 04:28 PM, Lukas Ocilka wrote:
On 07/31/2013 03:42 PM, David Majda wrote:
Hi,
we are pleased to announce that the final Ruby conversion of YaST YCP code to Ruby is over. The converted source was committed to Git [1], passed through Jenkins and builds successfully in YaST:Head [2]. YaST version was increased to 3.0.0. We also sent submit requests to Factory (not accepted yet).
Thanks to the team for all this awesome job! Well done! :) Congratulations, ycp killers!
Now it's time to think about what we want to do next, what are the next pain-points we want to solve - but this has to be discussed with all the team members together.
Are ycp-ui-bindings still used? Are they going to be replaced by ruby-ui-bindings?
They are still used as it is in fact yast-ui-bindings, it is connected to component system, not directly to ycp. Replacement could be in future, it depends how we decide. Josef
Cheers, Thomas
Bye Lukas
-- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Dne 1.8.2013 11:11, Thomas Goettlicher napsal(a):
On 07/31/2013 04:28 PM, Lukas Ocilka wrote:
Now it's time to think about what we want to do next, what are the next pain-points we want to solve - but this has to be discussed with all the team members together. Are ycp-ui-bindings still used? Are they going to be replaced by ruby-ui-bindings?
The overall YaST architecture is unchanged, we "just" replaced YCP with Ruby. The UI concept, SCR concept, modules/clients concept, etc... everything is the same as with old YCP. So now we have open doors, we are not limited by YCP anymore and we can do changes which were not possible with YCP. Now it's up to us which direction we choose next, what we want to improve or replace... -- Best Regards Ladislav Slezák Yast Developer ------------------------------------------------------------------------ SUSE LINUX, s.r.o. e-mail: lslezak@suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Dne 31.7.2013 15:42, David Majda napsal(a):
In the coming days and weeks, we would like to do the following:
1. Publish a document describing what the conversion changed (and how) and what remained the same. This will make starting with Ruby YaST easier for everybody who was not involved in the conversion.
This document is now available on YCP Killer project wiki: http://bit.ly/14l5rz9 Feel free to point out whatever you feel is missing. -- David Majda SUSE Studio developer http://susestudio.com/ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Hi, I have just finished installation of Factory snapshot with Ruby-YaST. It went smoothly, I did not hit any issue at all (however, I went through the default work-flow only). Huge THANKS to everybody involved in this project! Jiri On 07/31/2013 03:42 PM, David Majda wrote:
Hi,
we are pleased to announce that the final Ruby conversion of YaST YCP code to Ruby is over. The converted source was committed to Git [1], passed through Jenkins and builds successfully in YaST:Head [2]. YaST version was increased to 3.0.0. We also sent submit requests to Factory (not accepted yet).
** YaST Git repositories are open for development again. **
Thanks everybody for patience and welcome to the new Ruby era :-)
Technical Details -----------------
In all affected Git repositories, we used the following Git tags to mark the conversion:
* good-bye-ycp -- last commit before the conversion * hello-ruby -- last commit of the conversion
You can use them to see the changes the conversion did, e.g.:
https://github.com/yast/yast-yast2/compare/good-bye-ycp...hello-ruby
The amount of converted code is quite impressive:
* 4204 files * 594680 lines of YCP deleted * 724687 lines of Ruby added
Issues ------
There are few small issues that remain to be solved:
* There were problems running tests on Jenkins for several packages. We solved them temporarily by fiddling with the test scripts, but we need to fix them more properly. Josef & Martin will look into that.
Note the tests still pass correctly in when building in the OBS.
* Module "iplb" is currently broken -- it wasn't converted, but its tests don't work after converting "testsuite" into Ruby. We need to clarify status of this module and fix it or drop it.
Next Steps ----------
In the coming days and weeks, we would like to do the following:
1. Publish a document describing what the conversion changed (and how) and what remained the same. This will make starting with Ruby YaST easier for everybody who was not involved in the conversion.
2. Publish a document describing how to best handle YaST maintenance fixes in the old YCP code base which will need to be applied back to Ruby.
3. Decide on how exactly to do documentation and testing.
4. Update the skeleton that shows how to create a new YaST module to Ruby and describe the best practices.
5. Initiate a discussion about further changes and improvements in YaST architecture, which would allow us simplify it even more and make YaST even more attractive to contributors.
[1] https://github.com/yast/ [2] https://build.opensuse.org/project/show/YaST:Head
-- Regards, Jiri Srain Project Manager --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain@suse.com Lihovarska 1060/12 tel: +420 284 084 659 190 00 Praha 9 fax: +420 284 084 001 Czech Republic http://www.suse.com -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Op maandag 5 augustus 2013 09:20:54 schreef Jiri Srain:
Hi,
I have just finished installation of Factory snapshot with Ruby-YaST. It went smoothly, I did not hit any issue at all (however, I went through the default work-flow only).
Huge THANKS to everybody involved in this project!
Jiri
Thanks from me also. However the translators are faced with a _huge_ task to adjust in about 3300 messages in the yast po files the string "\n" by "\\n". This can be done by in a script using eg. sed. The uncertainty however is that we do not know if any other part of such a message is changed also. this means that we still have to check all these messages and remove the fuzzy indication by hand. Anyway there are also 37 messages without a previous translation. So apparently messages have been changed. Is it possible for the developers to mark messages in the pot files in which only "\n" has been changed into "\\n"? -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 08/05/2013 10:49 AM, Freek de Kruijf wrote:
Op maandag 5 augustus 2013 09:20:54 schreef Jiri Srain: Thanks from me also.
However the translators are faced with a _huge_ task to adjust in about 3300 messages in the yast po files the string "\n" by "\\n". This can be done by in a script using eg. sed. The uncertainty however is that we do not know if any other part of such a message is changed also. this means that we still have to check all these messages and remove the fuzzy indication by hand. Anyway there are also 37 messages without a previous translation. So apparently messages have been changed.
Is it possible for the developers to mark messages in the pot files in which only "\n" has been changed into "\\n"?
Please see this thread: http://lists.opensuse.org/yast-devel/2013-08/msg00019.html It seems to be a bug and Ladislav is checking that... We expect that instead of "\\n", "\n" is the correct format. Bye Lukas -- Lukas Ocilka, Cloud & Systems Management Department SUSE LINUX s.r.o., Praha -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Dne 5.8.2013 11:26, Lukas Ocilka napsal(a):
On 08/05/2013 10:49 AM, Freek de Kruijf wrote:
Op maandag 5 augustus 2013 09:20:54 schreef Jiri Srain: Thanks from me also.
However the translators are faced with a _huge_ task to adjust in about 3300 messages in the yast po files the string "\n" by "\\n". This can be done by in a script using eg. sed. The uncertainty however is that we do not know if any other part of such a message is changed also. this means that we still have to check all these messages and remove the fuzzy indication by hand. Anyway there are also 37 messages without a previous translation. So apparently messages have been changed.
I'm working on this issue. It turned out that the double backslash is a Ruby Gettext feature, when such POT file is formatted via rmsgfmt (Ruby Gettext equivalent to GNU msgfmt) the resulting MO file is correct. THis means that the POT file generated by rxgettext (Ruby Gettext) is not 100% compatible with GNU gettext, you cannot cannot mix Ruby and GNU gettext tools :-( Right now I'm tasting a patch to make the output optionally GNU compatible. For now ignore the backslash issue completely, we will need to regenerate all POT files again. Thanks! Ladislav -- Ladislav Slezák Appliance department / YaST Developer Lihovarská 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak@suse.com SUSE -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Dne 31.7.2013 15:42, David Majda napsal(a):
In the coming days and weeks, we would like to do the following:
[...]
2. Publish a document describing how to best handle YaST maintenance fixes in the old YCP code base which will need to be applied back to Ruby.
Available now: https://github.com/yast/ycp-killer/wiki/Porting-YCP-Patches-to-Ruby Since some of you already ported YCP patches to Ruby, I welcome any corrections, simplifications, etc. Feel free to edit the wiki or discuss here. -- David Majda SUSE Studio developer http://susestudio.com/ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
participants (8)
-
Arvin Schnell
-
David Majda
-
Freek de Kruijf
-
Jiri Srain
-
Josef Reidinger
-
Ladislav Slezak
-
Lukas Ocilka
-
Thomas Goettlicher