Hi,
The build 126 pkg(5) man page says about 'incorporate' depend actions:
If the value is 'incorporate', then the dependency is required,
but in addition, the version of the dependent package is
constrained. See 'Constraints and Freezing' below.
Of course the "Constraints and Freezing" section says "TBD" :)
However, I find that if I create a package with just "incorporate"
depend actions and install it, the packages specified in the depend
actions are not also installed.
Is this a bug in the man page or in pkg?
It seems to me to make the most sense as the man page describes. I'm not
sure what an "incorporate" action that *didn't* subsume "require" would
do in some cases.
For example, say I have package [email protected] installed locally, and the
publisher has [email protected], [email protected], and [email protected] available. Now I install a package
with a depend action that incorporates [email protected]. If incorporate doesn't
subsume require, what should happen? Should the installation fail?
Should A get upgraded to [email protected]? What about a case where I had [email protected]
installed initially (I'm not sure what happens in this case regardless
of whether incorporate subsumes require) - do we downgrade A? What
exactly is the definition of a depend action of type incorporate if it
*doesn't* subsume require?
I'm working on converting Sun Ray server software to IPS. I'd like to
offer a group package which has depend actions that cause all of the
packages which make up SRSS to become installed, so that people could
simply install that group package to get them all. In particular, I'd
like to ensure that the packages for a given build are all installed
together, since they'll have been tested together (our build number will
be part of our version - probably part of our component version but I'm
following your ON incorporation discussion closely where you're
currently proposing your build number to be part of the branch version).
Ideally I'd only have to express depend actions of type incorporate. It
would be inconvenient if I had to express depend actions of type
incorporate as well as actions of type require for each package. Should
that be necessary?
Note that currently if I express both require and incorporate actions
for a single package, pkg blows up with a RuntimeError exception of
"Duplicate Actions" in pkgplan.py:evaluate (line 152 in
[email protected]).
-Bob
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
