[...] $ osc meta prj KDE:Qt | grep description <description>This project provides the Qt 4.x.x version that is currently being considered most stable whilebeing reasonably recent. It is a good target to _aggregate or to build against if your particular project or application needs a newer version of Qt. Users are recommended to add this repository if they want to update their Qt.</description> $ osc meta prj KDE:Qt44 | grep description <description>This repository contains Qt 4.4.x</description> KDE:Qt has an updated but somehow stable Qt. KDE:Qt44… well, isn’t specified. If someone still has problems after adding KDE:Qt then there is another problem. A good bug report would make sense. The good news are that in the future we will not have this problem -> Duncan Mac-Vicar P.

There is no need to sign the service list, because the protection happens at the repository side still, so if a service tries to inject a “bad” repo, you will be warned anyway.

RedDwarf:

While services will be in openSUSE 11.1, We don’t know yet if there will be a service manager in YaST in 11.1.

Johan:

There is no need to add the repository permanently using 1 click install. You can deselect “remain subscribed”. You have to add the repo at least during install in case the packages depends on packages in the same repository. Otherwise, you can just use zypper and install the rpm remotely. It will check dependencies and install them, but if those dependencies are in that repo only, it will not succeed.

That service repolist on server, can it be signed? You know HTTP and DNS spoofing is a heartless bitch. Also, maybe in output of zypper repos, there should be visible which repository coming from service and which not.

btw, you can use ‘zypper ls -r’ (–with-repos) to show the services with their repos.