As @vtjnash suggests:
Something like ver(), that provides more complete information, would probably be nice to add. I currently can think of the following to include:
Is there any use in providing not only Base.libblas_name but also a version string for the blas library?
What would be great is if every library or module can register a version number, so that versions can be managed in a uniform way.
This seems like it should be integrated into require functionality, since that keeps track of what has and hasn't been loaded it should also keep track of what version was loaded.
Now that packages have taken the Julia ecosystem by storm, let's revisit this and possibly scope it down a little.
I suggest setting this pull request to track the creation of a ver() or version() call that returns information about Julia itself, and any libraries included. Packages can be handled with separately, this should specifically address @timholy's comment for a way to identify a particular Julia "release".
To that end, the list that Jeff started with seems pretty good, with Julia's commit hash, BLAS name/version, cpu and platform identifies. I can't think of anything else that might be interesting, can anyone else?
ver() function. closes #1351
also potentially useful (in verbose mode):
versioninfo() function. closes #1351
Revert "versioninfo() function. closes #1351"
This partially reverts commit bca3206.
This cherry-pick accidentally brought along versioninfo, which is a new
feature that shouldn't be introduced in a patch version.