On Dec 15, 2014, at 3:49 PM, Lawrence Velázquez wrote: > I don't think switching from "0.0.2" to "2014-12-15" (or whatever the > appropriate date is) would require increasing `epoch`, but I'm not sure.
You can check whether increasing the epoch would be necessary by using the vercmp procedure. I wrote a small wrapper script to be able to call it from the command line; you can get the script from my users directory in the repository: $ ~/macports/users/ryandesign/scripts/vercmp 0.0.2 2014-12-15 MacPorts considers 0.0.2 to be less than 2014-12-15. So no epoch increase would be necessary. On the other hand, at some point in the future, if a normal version number is assigned, increasing the epoch will be necessary: $ ~/macports/users/ryandesign/scripts/vercmp 2014-12-15 1.0.0 MacPorts considers 2014-12-15 to be greater than 1.0.0. On Dec 17, 2014, at 1:54 AM, Marko Käning wrote: > Well, it would be easier to simply use the date as the MP version number then. > > Yet, in order to not to initiate unnecessary rebuilds of the port, I am > reluctant to make this change now and wait for an update request from the > users > (for perhaps another half year) and then make the change. > > What do you say to that? I'm ok with that. _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
