[yast-devel] running YaST on Fedora Core 9
Hi! I compiled YaST and one yast module (yast2-iscsi-client as an example that it works) on Fedora Core 9: http://mzugec.blogspot.com/2008/05/research-of-possibility-running-yast.html This is of course only first step to make it really usable or really cross-distribution upstreamed tool. I compiled also libzypp/zypper and do some tests to compare their speed (installation source is local CD): [root@dhcp24 ~]# time echo "y"|yum install rpmlint Loaded plugins: refresh-packagekit fedora | 2.4 kB 00:00 updates | 2.3 kB 00:00 Setting up Install Process Parsing package install arguments Resolving Dependencies --> Running transaction check ---> Package rpmlint.noarch 0:0.82-3.fc9 set to be updated --> Finished Dependency Resolution Dependencies Resolved ============================================================================= Package Arch Version Repository Size ============================================================================= Installing: rpmlint noarch 0.82-3.fc9 fedora 178 k Transaction Summary ============================================================================= Install 1 Package(s) Update 0 Package(s) Remove 0 Package(s) Total download size: 178 k Is this ok [y/N]: Downloading Packages: (1/1): rpmlint-0.82-3.fc9.noarch.rpm | 178 kB 00:00 Running rpm_check_debug Running Transaction Test Finished Transaction Test Transaction Test Succeeded Running Transaction Installing: rpmlint ######################### [1/1] Installed: rpmlint.noarch 0:0.82-3.fc9 Complete! real 0m15.552s user 0m9.794s sys 0m3.801s And after uninstalling the same with zypper: [root@dhcp24 ~]# time zypper -n in rpmlint Reading installed packages... The following NEW package is going to be installed: rpmlint Overall download size: 178.0 K. After the operation, additional 178.0 K will be used. Continue? [YES/no]: yes Downloading package rpmlint-0.82-3.fc9.noarch (1/1), 178.0 K (178.0 K unpacked) Installing: rpmlint-0.82-3.fc9 [done] real 0m4.922s user 0m1.561s sys 0m2.610s That's great for us, isn't it? ;-) Bye, Michal -- Best Regards, Michal Zugec Software developer --------------------------------------------------------------------- SuSE CR, s.r.o. e-mail: mzugec@suse.cz Lihovarska 1060/12 tel: +420 284 028 960 190 00 Praha 9 fax: +420 296 542 374 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On 27.05.2008 at 23:54, Michal Zugec <mzugec@suse.cz> wrote: Hi! I compiled YaST and one yast module (yast2-iscsi-client as an example that it works) on Fedora Core 9: http://mzugec.blogspot.com/2008/05/research-of-possibility-running-yast.html
Machal, Did you have a look at the {zypp,yast}-backport [0][1] repositories in OBS? They compile zypper and yast also against Fedora and some feedback about those repos would in fact be great. Did you have anything special to do? Or could you mainly just go ahead and compile? Looking forward to hear your input (as one of the maintainers of those repos) Dominique [0] http://download.opensuse.org/repositories/zypp:/Backport/ [1] http://download.opensuse.org/repositories/YaST:/Backport/ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Machal,
Did you have a look at the {zypp,yast}-backport [0][1] repositories in OBS? They compile zypper and yast also against Fedora and some feedback about those repos would in fact be great.
No, I didn't know about them before. But I can see target Fedora (in version 8, I want current 9) with almost empty content ;-(. Only few packages are there. But this is probably Build Service problem, not your spec files Update: There is Fedora 9 now ;-)
Did you have anything special to do? Or could you mainly just go ahead and compile?
Mostly I just compile from sources. But about yast2-iscsi-client I must change and comment some distribution dependent code.
Looking forward to hear your input (as one of the maintainers of those repos)
I have some ideas. For instance we need for non-rpm distributions (yes, we want "expand" also there ;-)) custom pkg-bindings, and for Package[s] functions use map instead of string or list : instead of if( !Package::InstallMsg( "open-iscsi", _("<p>To configure the iSCSI initiator, the <b>%1</b> package must be installed.</p>") + _("<p>Install it now?</p>")) ) { Popup::Error( Message::CannotContinueWithoutPackagesInstalled() ); we should use if( !Package::InstallMsg( $["suse":"open-iscsi", "redhat":"iscsi-initiator-utils", _("<p>To configure the iSCSI initiator, the <b>%1</b> package must be installed.</p>") + _("<p>Install it now?</p>")) ) { Popup::Error( Message::CannotContinueWithoutPackagesInstalled() ); etc. Bye, Michal -- Best Regards, Michal Zugec Software developer --------------------------------------------------------------------- SuSE CR, s.r.o. e-mail: mzugec@suse.cz Lihovarska 1060/12 tel: +420 284 028 960 190 00 Praha 9 fax: +420 296 542 374 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On čt 29. května 2008, Michal Zugec wrote:
instead of
if( !Package::InstallMsg( "open-iscsi",
we should use
if( !Package::InstallMsg( $["suse":"open-iscsi", "redhat":"iscsi-initiator-utils",
This is still not very satisfying, Ideally, the ycp code should not care about the exact package names on different distros. Maybe there could be some dedicated layer, responsible for transformation of "suse" names to the real package name, available on the distribution which is curretnly running the code? j -- Jiri Suchomel SUSE LINUX, s.r.o. e-mail: jsuchome@suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Praha 9, Czech Republic http://www.suse.cz -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
participants (3)
-
Dominique Leuenberger -
Jiří Suchomel -
Michal Zugec