Version string patterns
Version string patterns
- Subject: Version string patterns
- From: Andrew Keller <email@hidden>
- Date: Mon, 15 Apr 2013 15:57:29 +0000
- Importance: Normal
- Sensitivity: Normal
Hello all,
I would like to fully understand the patterns and best practices used by version strings in OS X apps. I've been having trouble finding any hard documentation on exactly what patterns to follow, so I would like to bounce what I think I've learned off the list and see how much I got right.
BuildVersion: The build number on your CI server? Does anything in OS X use this? Are there any restrictions?
CFBundleShortVersionString: Human readable. Used when displaying versions. Typically something like 1.2.3d5. Integers are unlimited, stage code is usually 'd', 'a', 'b', or 'f' (or 'fc'?). Drop the stage code and the build number when on a real release.
CFBundleVersion: Machine comparable. Used by Installer.app when determining if copy X is newer than copy Y of an app. For KEXTs, use the same pattern as CFBundleShortVersionString, except that the bug version cannot be greater than 255. No specific pattern to follow for other types of products?
SourceVersion: The commit ID in the source repository? Does anything in OS X use this? Are there any restrictions?
Also, what's the difference between Info.plist and version.plist?
Thanks,
Andrew Keller
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden