On 04/29/2013 11:56 AM, Ladislav Slezak wrote:
Dne 26.4.2013 10:32, Ladislav Slezak napsal(a):
Dne 25.4.2013 16:53, Jiri Srain napsal(a): [...]
The more difficult part will be migration of data created on run-time...
BTW another option is to leave the YCP parser in .target.ycp agent and leave the code as it is now. The agent is independent part of YaST (it just reuses the YCP parser library) so we could leave YCP support in SCR but remove it from the interpreter.
We could change the data where possible and leave the complex cases unchanged.
This is still open and we need to actually define how much we want to "kill" YCP...
If we want to kill YCP, I'd prefer to kill it completely. YaST package should know where these YCP files are stored, converting the data during package upgrade (in %post) sounds like a good idea. Data IMO represent a single variable (hash, array, ...) so it's not a complete code actually. Writing a script for converting them should not be that hard and we could put it into the YaST Base package or into a special one if you prefer. The updated package would need to have the script (package) in "pre-requires". 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