On Feb 28, 2006, at 3:16 AM, Martin Costabel wrote:
In very old versions of fink, the search order used to be from left to right in the Trees line (or so the documentation said). Nowadays it seems to be from right to left. This is, of course, not reasonable, given that local/main is by default still the first item on that line but should be searched first.
Yes, .info files in trees on the right override trees on the left. You're right about the positioning of local/main on the left, thanks for pointing that out. But then local/injected is on the right but should also be high-priority, so left-to-right doesn't work too well either. What do you think the correct precedence should be?
In reality you should not depend on that search order. It is not only at build time where this can lead to confusion. Also at install time, if you built packages with identical version-revision in two different trees, you have to pray that dpkg finds the right one of the deb files with identical names.
When Fink runs dpkg, it will always install the .deb corresponding to the .info with highest precedence. But you're right in the general sense, for example apt-get may become confused.
The better solution is to increase the revision for the info file in your local tree: If you have foo-1.2-3 in unstable, make it foo-1.2-3.0 or similar in local. This has the advantage that once the revision in unstable is increased to foo-1.2-4, it will supersede the one in local, which is often what you want.
Exactly. The "primary directive" of Fink is that identical version/ revision means an identical .deb. This prevents much breakage, and keeps things predictable.
Dave
PGP.sig
Description: This is a digitally signed message part
