Jens Elkner wrote: > 'James Carlson wrote:' >> Jens Elkner writes: >>> Is anybody able to explain, why SUNWcsl has no dependency on SUNWsasl >>> defined? >> What "SUNWsasl"? Are you referring to the Sun One Directory Server? > > Ooops, sorry - SUNWlibsasl of course! > >>> Actually, if one pkgrm SUNWsasl (because unusable wrt. sendmail - one has >>> to build and install the real cyrus-sasl), the user gets no warning (not a >>> single Sol10/Nevada package has a P SUNWsasl). But after the removal, >>> nobody is able to login, because the pam stuff depends on libldap.* >>> (doesn't matter, whether one uses ldap maps or not), which in turn depends >>> on libsasl. >> libsasl comes from SUNWlibsasl on Solaris, and it's in SUNWCmreq (the >> "Minimal Core System Support" metacluster), which means that it >> _cannot_ be removed from a supported system and thus requires no >> explicit dependencies. > > Unfortunately the running system has no idea wrt. to clusters. And no-one > should expect an user/admin to inspect the .clustertoc, before he removes > a from the running system as unused reported package. > Compared with Linux, Solaris seems still to live in the stoneage: > The package system provides the opportunity to record dependencies, > but it seems to be rarely used (perhaps because the developer think, > the initial install program needs to know about the deps, only)... >
Yes, we're painfully aware of this problem and are trying to attack this for Solaris Nevada. Much needs to be done. - Bart -- Bart Smaalders Solaris Kernel Performance barts at cyber.eng.sun.com http://blogs.sun.com/barts
