Mailinglist Archive: yast-devel (177 mails)

< Previous Next >
Re: [yast-devel] Direction of YaST Architecture?

Hello,

On Jan 30 14:35 Stanislav Visnovsky wrote (shortened):
On piatok 28 Január 2011 16:50:10 Arvin Schnell 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.

For me this looks like a contradiction in itself because
killing YCP would kill all code which is written in YCP.

Stanislav,
what did you actually mean?


In general I think we should be very careful with exact wording.
I.e. what exactly is menat with "YCP"?
The language?
The YCP runtime environment?
The code which is written in YCP?


I think before any discussion whether or not "YCP" can be replaced
makes sense, there would have to be at least one single alternative
which really actually works and which is already accepted by the
free software developers "out there" who like to contribute to YaST.

If and only if such an alternative exists, then it could make sense
to set YCP "deprecated" so that no new YaST module would be created
in YCP code.

Then there would be a longer time of a "YCP fade out phase"
where the YCP runtime environment must be maintained
so that the old YCP modules can still run.

During the "YCP fade out phase" the old YCP modules could be
one by one and step by step re-written in whatever alternative
language.


Personally I don't care about alternative languages as long as
the alternative really actually works.
I trust that any decision of free software developers who actually
contribute to YaST would be also o.k. for me.


Kind Regards
Johannes Meixner
--
SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany
AG Nuernberg, HRB 16746, GF: Markus Rex
< Previous Next >
List Navigation
This Thread
Follow Ups