> That sounds like a good suggestion. However, this is more complex as you > could be installing either trunk or a beta/release candidate of the > current branch. Also the current version never knows what the next > version will be called, so that has to be handled on the server side. > > I don't think a simple --pre would be enough, rather we would need a > fixed list of "beta", "rc", or "testing" maintained with symlinks or > specify the exact version number of the tarball.
KDE partitions the 80 and 90s series numbers to indicate alphas and betas (like our current 99). By expanding beyond just 99, this gives more pre-release numbers to track and allows keeping them in order with minimal overhead.
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
