On Tue, 16 Apr 2013 10:02:29 +0200 "Michal Filka" <michal.filka@suse.cz> wrote:
I assume that we will need to maintain ycp and ruby code for some time together (SLE SP3, SP4). So, I'd like to know if it is possible to use ycp killer for converting patches.
I agree, that it makes hard to convert patches. But on other side, for me more important is to properly make such patch. So in ruby you can very intensive test such change and behavior and then do such change in ycp should be relative easy. Or other way when you have patch for ycp, then you should write test for problematic part that demonstrate problem in ruby and then just implement it.
Doing a work twice is always problem ;-) I see two ways: - translate whole module again after each patch in ycp. Problem is potential loss of changes done in ruby code only.
Yes, you will loose changes in ruby. Only possible way that cames to my mind is to repeat translation, create patch again original translated ruby and try to apply it to master. There is more potential way how to do it.
- translate the patch only (if possible) and try to integrate it somehow by hand.
you cannot translate only patch, as ycp is really dependent on context, so only way I describe above is possible or do it twice.
Another note is loss of history in github.
It is just partially true. You don't lost history, it just add one more step, when you need to check old ycp code that match ruby code and see history in ycp.
This becames to be a problem in case of refactoring in ruby code.
But you have same problem in ycp, I don't know any version control tool that can track all code refactoring. It is not problem of ruby.
Michal
-- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org