Tom Mueller (pkg-discuss) wrote: > Based on a discussion about depend actions back in May/June [1], my > understanding is that a depend action with type=require is supposed to > specify the minimum version that is needed to satisfy a dependency. > > So given a repository with: > > pkg:/[EMAIL PROTECTED] > pkg:/[EMAIL PROTECTED] > pkg:/[EMAIL PROTECTED] with a depend action, type=require fmri=pkg:/[EMAIL > PROTECTED] > > When I install bar, what version of foo should be installed? Currently, > the code is installing [EMAIL PROTECTED] An image-update will then update > foo to > 1.4. > > Is this a bug? > > If it's not a bug, how does one specify a dependency on a minimum > version of a package, but when the package is installed, you want the > most recent version of the dependency installed? > > Thanks. > Tom
Hmmm... right now we're proposing the latest version that matches the dependency that is specified. This likely to continue working this way for a bit, until we have a more complete solution for evaluating complex constraints. Right now we have no effective way of backtracking, so if we see a min dependency of 1.3, if we select 2.0 but later uncover a new incorporation dependency at 1.4 we're stuck, so I wrote the code to be conservative about proposing forward movement. We're exploring the use of a constraint solver, but that's not this release. - Bart -- Bart Smaalders Solaris Kernel Performance [EMAIL PROTECTED] http://blogs.sun.com/barts "You will contribute more with mercurial than with thunderbird." _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
