On Wed, May 14, 2008 at 03:34:46PM -0700, Bart Smaalders wrote: > > P.S. We are planning for introducing updates into the Glassfish V3 > > repositories, some of which introduce incompatible change that require > > multiple packages to be updated at the same time. I was hoping that we > > could use incorporations to force the updates to happen in this way. > > Right now incorporations just specify a minimum dependency; this is a > missing feature and will get fixed soon.
(I found this old thread whilst trying to read up about how dependencies are supposed to work.) When you say "will be fixed", do you mean "allow to specify a maximum dependency", as the source seems to indicate, or something else? If it's the former, then I don't quite understand how incompatible versioning is represented in pkg. For example: glassfish-user is released, depends on [EMAIL PROTECTED] [EMAIL PROTECTED] is released, not compatible If [EMAIL PROTECTED] can be upgraded into [EMAIL PROTECTED], then glassfish-user breaks (I'm presuming that at publication time that package has no idea that [EMAIL PROTECTED] is going to be released). Probably the argument is that version 5 needs to be a separate package instead, since it introduces incompatibilities? If so, how would the system deal with things like "give me glassfish"? Some kind of incorporation that matches either [EMAIL PROTECTED] or [EMAIL PROTECTED] thanks john [1] related question, is there a plan for where this versioning goes in the FMRI? _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
