On Oct 9, 2006, at 8:23 PM, Blair Zajac wrote:
When I'm developing a new port or want to override the default port in MacPort's svn with a local port of a newer upstream release, it would be nice to have a range of revision numbers that is smaller than any revision number from MacPort's svn repository.
Well, to keep revisions sacrosanct , which kvv argues for and I agree with, another option might be to use small negative epoch values. I believe epoch defaults to zero. So if you used a small negative epoch for your internal development, and removed epoch on release, I believe you'd have a solution to your problem. Assuming that all the epoch comparisons work correctly for negative numbers, which they probably do. You'd need to do some testing to figure verify this. The nice thing, of course, is that maps well to the intended use of epoch: version numbering in entirely different spaces. James
This would enable me to have a local port, say subversion 1.4.1-0, and then when the real subversion 1.4.1-1 comes out, I'll get an out of date warning.
Also, is the revision an integer, a floating point value, or does it compare values like the version number, it 0.10 is greater than 0.9?
Would people mind defaulting the revision to 1?
I don't know how this would be rolled out. It would cause a massive upgrade.
Regards, Blair
-- Blair Zajac, Ph.D. CTO, OrcaWare Technologies <blair@orcaware.com> Subversion training, consulting and support http://www.orcaware.com/svn/
_______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-dev