Trying to install a package that requires one or more dependencies through package-manager fails. For example:

- Download Skype rpm and save it to the desktop
- Single/Double click on it: "/sbin/yast2 --install" will be called
- installation will not complete due to missing libsigc package (without any error message). Obviously if that package is already installed, all will be correctly done.

If, following the above example, Skype rpm is installed through KRPMView for example (open the rpm through Konqueror, then click on "Install package with Yast"), all dependencies are resolved correctly and the package is installed.

Reading the /sbin/yast2 --help output:

<package> can be a single short package name (e.g. gvim)
which will be installed with dependency checking, or the full
path to an rpm package (e.g /tmp/gvim.rpm) which will be
installed without dependency checking.

If "yast2 --install" can't resolve dependencies for such packages and cannot be patched (strange behavior in my opinion...), it should be avoided in favour to other methods, as KRPMView for example. An user will be disoriented if he simply clicks on an rpm and it doesn't install without any error message (and the menu entry says "Open with Software Installer" if the user right-clicks on a rpm...)