----- [email protected] wrote: > Thanks for all the replies.. Now that I have a better understanding, > > I have a really basic question. > > Why is mtst dependent on osnet-incorporation. > > mtst's manifest file doesn't include that dependency. And when I look > > at the logs, it's actually added during pkgmogrify. > > --- > depend fmri=consolidation/osnet/osnet-incorporation type=require > license system-fault-management-mtst.l > license=system-fault-management-mtst.l > --- > > Where is this coming from? > > I understand that 2 more dependencies are found using pkgdepend and > those look reasonable, but I do not understand why onset-incorporation
Packages that are incorporated depend on the package that incorporates them, so that if you install them the incorporation is also installed. This ensures that (as an example) if you install mtst, then all of the other packages in osnet will also be from the same build. If packages from the osnet consolidation did not have a dependency on osnet-incorporation, then install and update would mix and match different versions of osnet packages from different builds, which is obviously unlikely to work. The incorporations define a surface that constrains a set of packages such that when installs or updates are performed, all of the packages that are incorporated move forward and backward together. -Shawn _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
