The file http://fink.sourceforge.net/CURRENT-FINK reads 0.5.4.
This has the consequence that users trying to do selfupdate (point-release) from before 0.5.4 remain blocked on 0.5.4.
Is this intentional?
Yes. Fink 0.5.4 contains a "fink" program that knows how to search for the current version based on the tree you're using. Once you've updated to 0.5.4, fink will never look for CURRENT-FINK anymore, it will look for CURRENT-FINK-<TREE> instead; the old one's there basically for upgrade purposes.
If you have gcc 3.3, the tree is "10.2-gcc3.3", so it would look at CURRENT-FINK-10.2-gcc3.3 (which says 0.6.2), if you don't, the tree is "10.2" so it would look at CURRENT-FINK-10.2 instead (which says 0.5.4).
Basically, people who are stuck at 0.5.4 are not using gcc3.3; since Fink only officially supports gcc3.3 now, they're basically frozen in the same way 10.1 users can still use fink, but it's very old and out-of-date, and is not getting updated. :)
-- Benjamin Reed a.k.a. Ranger Rick -- http://ranger.befunk.com/ gpg: 6401 D02A A35F 55E9 D7DD 71C5 52EF A366 D3F6 65FE You had me at HELO.
pgp00000.pgp
Description: PGP signature
