Hi Juan, > My current idea is to create a base/config/macports_version file holding > something like 1.6.1, but the selfupdate > logic of reading the latter over base/config/mp_version has to be > thoroughly thought out: 600 (from base/config/mp_version's 1.600) > is greater than 6, so if we flat out select base/config/macports_version > to read the new version we will break > selfupdating for everyone, as rpm-vercomp will not see 1.6.1 as greater > than 1.600.
Why don't we just hold off on applying this fully until we decide to release 2.0, whenever that may be? Surely we just avoid this problem then. Kind regards, Maun Suang _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-dev
