[yast-devel] UI::SetModulename
packager module does not compile against latest core, pkg-bindings, anyone has idea where to look? (i commented it to make it work, but why is it failing?) What is the replacement for that function? ProductLicense.ycp:18 [Interpreter] Symbol 'UI::SetModulename' does not exist. cheers Duncan -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Hi Duncan,
packager module does not compile against latest core, pkg-bindings, anyone has idea where to look? (i commented it to make it work, but why is it failing?)
ProductLicense.ycp:18 [Interpreter] Symbol 'UI::SetModulename' does not exist.
Yes, it is because of UI::SetModulename builtin. It has been dropped. Afair, only yast2-network and Wizard used it, but in turn (almost) every module uses Wizard. It breaks binary compatibility of .ybc files and that's why so many modules did not build.
What is the replacement for that function?
I'm afraid there is no known (YCP) replacement of this function, it has been obsoleted. Maybe there is something in new YCommandLine, but I doubt it's accesible from YCP. HuHa should know more ... B. -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Am Montag, 18. Februar 2008 schrieb Katarina Machalkova:
Hi Duncan,
packager module does not compile against latest core, pkg-bindings, anyone has idea where to look? (i commented it to make it work, but why is it failing?)
ProductLicense.ycp:18 [Interpreter] Symbol 'UI::SetModulename' does not exist.
Yes, it is because of UI::SetModulename builtin. It has been dropped. Afair, only yast2-network and Wizard used it, but in turn (almost) every module uses Wizard. It breaks binary compatibility of .ybc files and that's why so many modules did not build.
I'm afraid there is a severe reason that that: yast2.rpm can't build because network requires wizard requires cwm requires network - it's impossible to bootstrap since r44468 | mzugec | 2008-02-14 17:35:59 +0100 (Do, 14 Feb 2008) | 2 lines Geänderte Pfade: M /trunk/yast2/VERSION M /trunk/yast2/library/wizard/src/Confirm.ycp M /trunk/yast2/package/yast2.changes added Confirm::RunningNetwork() for bnc#360571 Greetings, Stephan -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On Monday 18 February 2008 19:26, Duncan Mac-Vicar Prett wrote:
packager module does not compile against latest core, pkg-bindings, anyone has idea where to look? (i commented it to make it work, but why is it failing?)
What is the replacement for that function?
It's obsolete and dropped from the UI. It hadn't done anything useful for a long time. I removed all calls (in 2 or 3 places overall) in the YCP code; bubli and mvidner had found 2 more, and we removed them, too. "grep" doesn't find any more call in the sources.
ProductLicense.ycp:18 [Interpreter] Symbol 'UI::SetModulename' does not exist.
Maybe we simply need to resubmit some packages. CU -- Stefan Hundhammer <sh@suse.de> Penguin by conviction. YaST2 Development SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Nürnberg, Germany -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
participants (4)
-
Duncan Mac-Vicar Prett -
Katarina Machalkova -
Stefan Hundhammer -
Stephan Kulow