Arvin,
thanks a lot for stepping forward and starting this dicussion !
* Arvin Schnell aschn...@suse.de [Jan 28. 2011 16:50]:
So what seems desirable and feasible? Some ideas:
Which goals would you achieve by implementing these ideas ?
1) Replace YCP with some common language? With more
* Arvin Schnell aschn...@suse.de [Jan 31. 2011 10:54]:
The currently generated bindings for libstorage are so bad that
almost every function has handwritten make-it-usable-code in
YCP. This hinders moving code from YCP to C++. Apart from that we
even need workarounds in libstorage to avoid
On Friday, January 28, 2011 04:50:10 pm Arvin Schnell wrote:
So what seems desirable and feasible? Some ideas:
1) Replace YCP with some common language? With more that 100
modules this looks impossible.
2) Allow a common language next to YCP? A good integration seems
difficult.
On Mon, Jan 31, 2011 at 10:53:51AM +0100, Klaus Kaempf wrote:
Arvin,
thanks a lot for stepping forward and starting this dicussion !
* Arvin Schnell aschn...@suse.de [Jan 28. 2011 16:50]:
So what seems desirable and feasible? Some ideas:
Which goals would you achieve by
Duncan Mac-Vicar P. write:
I would suggest a step by step reborn instead of a replace by
something we will write from scratch someday but does not exist yet.
Taking the bests parts of it (libyui) plus support for a couple of more
popular languages, and rethinking some parts like SCR, or
On Monday 31 January 2011 11:10:55 Thomas Goettlicher wrote:
On Friday, January 28, 2011 04:50:10 pm Arvin Schnell wrote:
So what seems desirable and feasible? Some ideas:
1) Replace YCP with some common language? With more that 100
modules this looks impossible.
2) Allow a
On Jan 30, 2011, at 6:35 AM, Stanislav Visnovsky wrote:
1) Replace YCP with some common language? With more that 100
modules this looks impossible.
I think this is a good and the only viable option if YaST code should survive
in long run.
+1.
--
To unsubscribe, e-mail:
On Jan 31, 2011, at 5:03 AM, Josef Reidinger wrote:
- Use a couple of languages people know and like
Maintenance nightmare E.g. I don't have problem to maintain projects in
different languages ( now RoR, perl and YCP), but if I am maintaner and
someone leave or move to another team
On Sun, Jan 30, 2011 at 02:35:26PM +0100, Stanislav Višňovský wrote:
So what seems desirable and feasible? Some ideas:
1) Replace YCP with some common language? With more that 100
modules this looks impossible.
I think this is a good and the only viable option if YaST code should
