pkg:/system/security/kerberos-5
pkg:/service/security/kerberos-5
pkg:/system/security/kerberos-5 appears to bundle mostly things
associated with the KDC aspect of Kerberos and
pkg:/service/security/kerberos-5 is stuff associated with Kerberos
clients. There appear to be some anomalies with the contents however.
For example usr/sbin/kclient is in pkg:/system/security/kerberos-5 but
this should really be in pkg:/service/security/kerberos-5. There are
several other items that should also be moved around. What we are
unsure however is what was thought behind the original construction of
these packages contents? Can we reorganize these packages into
everything needed by krb clients into one package and the additional
stuff to provide KDC support in the other or would that violate some new
pkg standard? And if we do this it would be good if we could rename the
packages to reflect this.
By all means, refactoring things along client and KDC boundaries make
sense. The original IPS packages were constructed by taking one or
more SVR4 packages and combining them and there definitely may have
been some issues introduced in doing so. In addition, many of the
packages weren't correctly factored originally.
Looking at packages as supported minimization boundaries, feel free to
propose two or more package definitions and post their manifests and
proposed names here for review. Keep in mind the way the dependencies
point (although IPS supports dependency loops, they reflect two
packages that in most cases can/should be combined.)
_______________________________________________
on-ips-dev mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/on-ips-dev
