Todd Pisek wrote:
I can add checks into the file system specific installation code to check for the other package and take appropriate action (not yet determined) if necessary. I was just curious what IPS offered.
IPS will provide exclude dependencies before we're done. However, the customer impact is awkward with packages such as yours that delivers the same functionality in two forms. Suppose I have another package X that requires QFS. Since both samfs and qfs packages deliver this functionality, we now need to add a new dependency type of "either samfs or qfs", otherwise installing X will prevent customers from installing samfs or would require them to do so...
It revolves around license fees. I'm not sure how licensing works for Solaris 11, but it's the same code base as Solaris 10.
Life would be much simpler if you just always shipped SAMFS versions of QFS in QFS, but left the key enabler component in the SAMFS package. - Bart -- Bart Smaalders Solaris Kernel Performance [email protected] http://blogs.sun.com/barts "You will contribute more with mercurial than with thunderbird." _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
