Just had a try on TW with current libzypp/zypper packages. # rpm -q libzypp libzypp-17.11.0-1.1.x86_64 # rpm --changelog -q libzypp [...] * Mo Dez 10 2018 ma@suse.de - commit: set `SYSTEMD_OFFLINE=1` during chrooted commits (bsc#1118758) - no-recommends: Nevertheless consider resolver namespaces (hardware, language,..supporting packages) (FATE#325513) - BuildRequires: libsolv-devel >= 0.7.2 (SOLVER_FLAG_ONLY_NAMESPACE_RECOMMENDED) - Remove world-readable bit from /var/log/zypp (bsc#1099019) - version 17.10.2 (9) # rpm -q zypper zypper-1.14.19-2.1.x86_64 # rpm --changelog -q zypper [...] * Di Dez 11 2018 ma@suse.de - no-recommends: Nevertheless consider resolver namespaces (hardware, language,..supporting packages) (FATE#325513) - BuildRequires: libzypp-devel >= 17.10.2 - version 1.14.18 # zypper inr Loading repository data... Reading installed packages... Resolving package dependencies... The following 5 NEW packages are going to be installed: nvidia-computeG05 nvidia-gfxG05-kmp-default nvidia-glG05 suse-prime x11-video-nvidiaG05 5 new packages to install. --> Looks good. As before. # zypper inr --no-recommends Loading repository data... Reading installed packages... Resolving package dependencies... The following NEW package is going to be installed: nvidia-gfxG05-kmp-default 1 new package to install. Makes sense, since nvidia-gfxG05-kmp-default recommends nvidia-glG05, x11-video-nvidiaG05. And x11-video-nvidiaG05 recommends nvidia-computeG05 and suse-prime in addition. BUT, there is no autoselection of any NVIDIA driver package when using YaST2. Even not when enabling: --> Extras/Install All Matching Recommended packages.