Dave Miner wrote:
Bob Doolittle wrote:
Dan Price wrote:
On Fri 30 Oct 2009 at 01:57AM, Bob Doolittle wrote:
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?
I believe the man page is wrong, please file a bug. For example,
'entire' incorporates every package in what used to be called "the WOS"
but doesn't require them to be installed.
Incoporations are typically used to tie packages together such that
they form a versioned "surface"-- as Liane has smartly put it-- an
incorporation should define what you test as a unit.
OK, but that doesn't address the rest of my issues. If incorporate
doesn't require packages, then what's the recommended way to express
both - that you want a specific (set of packages on a) versioned
surface to be installed? Is it also a bug that including both
incorporate and require dependencies in a package causes a "Duplicate
actions" exception? Or do we intend to require two separate packages
- one incorporation to express the versioned surface and another to
require the packages from that surface that you want? Why would we
force this to be two separate packages?
Right now, that's what is done.
If depend actions of type=incorporate and type=require are really
separate actions, then a "Duplicate actions" exception is surprising.
Is this behavior we think worth specifically retaining for some reason,
or do we consider this a bug?
It sounds like an incorporation is intended to be broader (potentially)
than an install cluster (aka 'group package') such as babel_install or
slim_install.
What happens in this situation:
I have a...@4 installed
I install an install cluster requiring b...@3 and c...@3, and an incorporation
of a...@3, b...@3, and c...@3
The repo has a...@3, a...@4, b...@3, and c...@3
During the planning phase pkg presumably will notice that the installed
a...@4 does not meet the incorporation constraint of a...@3.
Does it:
- fail the install, or
- downgrade to a...@3
In other words, do violations of incorporation constraints initiate
package actions (assuming the repo can support them), or only errors?
Thanks,
Bob
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
