Bart Smaalders wrote:
Todd Pisek wrote:
Suppose I have two packages called X and Y. I want to make these
packages mutually exclusive. That is, if X is installed, Y can't be
installed and vice versa.
Once we have the SAT solver in, we can implement an exclude
dependency... but these are pretty difficult for people to
deal with in most cases; they cannot be easily automated.
We have traditionally packaged two variants of the the QFS file
system code and its associated archiver/HSM (Hierarchical Storage
Manager). The
sam-qfs package had SAM (the archiver/HAM) and QFS. The QFS package is
just QFS. SAM is tightly woven into QFS. While I'm sure it technically
feasible to separate the two, it is non-trivial and there are no plans
on our current road map to perform such a separation.
Did you provide just QFS because of entitlement reasons, or is there
another reason to maintain and test two different versions of the same
binaries?
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.
The archive component (SAM) has additional modules, but it also has
additional code in common with QFS. That is why I mentioned that
separation is non-trivial. The two packages have different SVR4 package
names (SUNWsamfs and SUNWqfs) so much of the code lands in their
respective directories. The collisions occur in the common areas (man,
drv, etc.).
We like to discourage exclude dependencies, because the packaging system
doesn't understand what to do when it encounters one other than to stop
and fail the action.
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.
--- Todd
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
