Hi,
This is a question to the old YaST hackers:
I heard the rumor that there once was a policy that YaST packages should
not require other (non-YaST) packages directy but rather do a check at
runtime if everything is there and ask to install packages if missing.
There are valid use cases for this where I can see that this makes
sense, eg. you configure the user authentication method LDAP and
pam_ldap is missing. It does not make sense to include pam_ldap then in
some YaST package because it is required due to a configuration
setting.
My question relates to yast2-x11 where the first action of the module
is, to check if its required packages are there.
IMHO these packages should be required by the package directly.
Btw. packages that do not exist at all are filtered out of this list.
If these packages for some reason are not available for the current
architecture or system then this very YaST module should not have been
installed in the first place.
So my question (finally) is:
Are there any technical reasons (and what exactly) why we used to do it
this way over the years or will it hurt anybody if I require the needed
packages directly??
Thanks for your comments.
(even if it reads: Why do you ask, just fix it!)
Ciao,
Daniel
--
J. Daniel Schmidt