On Mon, Feb 20, 2012 at 05:07:39PM +0100, Konrad Hinsen wrote: > John J. Foerch writes: > > > That $CONKEROR_SHORT_VERSION$ thing was a leftover from our versioning > > system of several years ago. I've removed it now, and put 1.0. I'm not > > Sounds fine. > > > really sure what this key is for, and whether the value I put for it is > > right, or how it is different than the regular version, which is 1.0pre. > > CFBundleShortVersionString is the kind of version number shown to a user, > whereas CFBundleVersion is an internal "build number" used to identify > a specific build uniquely but considered too much information for the > ordinary user. I am not trying to defend this distinction, which doesn't make > much sense in many situations. > > What matters for us is that CFBundleVersion should consist of comma-separated > integers, which rules out 1.0pre. Apparently nothing bad happens if this rule > is ignored, but who knows. CFBundleShortVersionString should consist of > exactly > three comma-separated integers. > > MacOS doesn't care much about version numbers anyway, they are there > to be shown to the user and to be obtained by system administration > tools. > > I'd set both to 1.0.0 and forget about this until there is a release > 1.0 of Conkeror. Or interpret the rules creatively: nothing forbids > negative integers, after all, so why not use 1.0.-1 for pre-release code?
Will anything blow up if I set it to "1.0pre"? That is our version number, so that is what users should see. I don't want users reporting anything but our standard version number to me when they ask questions. It is astounding to me that Apple seems to think they can dictate their One True version format to the world.. we use a very widely accepted convention. -- John Foerch _______________________________________________ Conkeror mailing list [email protected] https://www.mozdev.org/mailman/listinfo/conkeror
