| commit | 8b4a12a25b4d069fd09e6a7444f33e33d50d43f8 | |
| author | Damian Johnson <atagar@torproject.org> | |
| Sun, 22 Jul 2012 03:23:54 +0000 (21 20:23 -0700) | ||
| committer | Damian Johnson <atagar@torproject.org> | |
| Sun, 22 Jul 2012 04:54:45 +0000 (21 21:54 -0700) | ||
| tree | f6522c897f810ca4da1d27d13376feea83e1fce1 | treesnapshot (tar.gz zip) |
| parent | 3eb0fd50476d893264bc1fdf6efe675efe815141 | commitdiff |
Adding an EXTRA_INFO attribute to tor versions
Tor versions often contain information about the SCM commit they came from, for
instance...
0.2.3.16-alpha-dev (git-8be6058d8f31e578)
This isn't part of the spec, which in turn choked stem when I tried to parse
those versions. Adding this in and better defining a couple other points...
- The STATUS_TAG should only contain non-whitespace. Otherwise... well, just
about *anything* could be a 'valid' status tag.
- The spec says that status tags should be "compared lexically". The ASCII
value of 'Z' is greater than 'A' so I guess this means that they're sorted in
a reverse alphabetical order. This seems weird, but clarifying it.
Tor versions often contain information about the SCM commit they came from, for
instance...
0.2.3.16-alpha-dev (git-8be6058d8f31e578)
This isn't part of the spec, which in turn choked stem when I tried to parse
those versions. Adding this in and better defining a couple other points...
- The STATUS_TAG should only contain non-whitespace. Otherwise... well, just
about *anything* could be a 'valid' status tag.
- The spec says that status tags should be "compared lexically". The ASCII
value of 'Z' is greater than 'A' so I guess this means that they're sorted in
a reverse alphabetical order. This seems weird, but clarifying it.
| version-spec.txt | diffblobblamehistory |