What I think it *should* do is:
Resolve all dependencies, choosing the latest versions which cause no
conflicts for the entire set of transitive dependencies. I.e. the same
thing a strict resolve does, but if a conflict would have happened,
instead try the next newest version, and so on, until a compatible set
of versions are found.
One can imagine there are a lot of edge cases and implementation details
in this, the description is just from a user perspective, what the user
sees. If it doesn't work like this, I would be very interested in how
it does work, because this is my understanding of what it does, having
never actually read the code (yet).
-Carl
On 09/24/2010 07:54 AM, Archie Cobbs wrote:
On Fri, Sep 24, 2010 at 9:32 AM, Mitch Gitman<mgit...@gmail.com> wrote:
But Archie, can you or anyone else articulate in your own words the rules
of
latest-compatible? The current brief description in the documentation can
be
interpreted to mean anything. I would find it troubling if the maintainers
of an open-source framework are moving to a different default behavior, and
no one can put in plain English what that default behavior does.
I agree with that and would also like to understand the algorithm that
latest-compatible uses before we decide to inflict it on everyone.
Hopefully someone will explain it to us, otherwise I guess I'll have to do
some code diving... :-)
-Archie
--
Carl Myers
Palantir Technologies | Internal Tools Software Engineer
cmy...@palantir.com
