On Saturday, 22 June 2019 00:35:25 -03 Stasiek Michalski wrote:
This is not an issue with recommends, you can't remove XDM even if you wanted to, because xdm holds the base scripts that start other stuff, because update-alternatives handling. Fixing that will require a little bit more than just removing recommends. This will certainly also make dropping Xorg from Factory in 50 years harder than it needs to be ;) I told you I probably made some mistakes :)
But, I only installed KDE patterns and even so, I had both SDDM and LightDM. I think this is because lightdm is recommended by patterns-base-x11 which I have installed.
I don't really see that looking at the zypper search results:
zypper se --recommends systemd-32bit
S | Name | Summary | Type --+----------------------------------+------------------------+--------
| patterns-base-minimal_base-32bit | Minimal Appliance Base | package | patterns-media-rest_cd_core | Remaining Software | package | patterns-media-rest_core_dvd | Remaining Software | package
by the looks of it, those patterns are required or recommended by nothing, unless I'm missing something. Yes I checked that as well, I don't have those patterns installed.
- I'm currently a ZSH user, but when I first installed Tumbleweed I had at least three shells installed (bash, zsh, tcsh) why?!
tcsh is required, not recommended by cvs: https://build.opensuse.org/package/view_file/openSUSE:Factory/cvs/cvs.spec
cvs (and git-cvs) in turn is recommended by git, which is not installed by default with any default system role afaik. Yes that was git recommending cvs recommending tcsh.
This will break a few things, for example in case of branding packages, we don't really need to have branding elements installed on a server installation, so instead of using direct dependencies for the 'distribution-logos-openSUSE' packages (there are 4), recommends are used to install the correct one by the product packages. Now you might be asking, why isn't this handled with supplements, so differentiation between Kubic and MicroOS isn't done by the product package (they share the same one), but by different set of components, which means that if it was done through supplements, we would have a bunch of stuff conflicting with each other. You should probably talk with people that manage Kubic and MicroOS stuff though, I'm not enough of an expert in the area ;)
And obviously, if anybody has a better idea, I'm open to anything, because that's just a mess :P OK, for branding packages makes sense to not have "hard dependencies" but for all other patterns they do.
Also, I wasn't aware about Supplements or how do they work. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org