| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| |
|
|
|
|
|
|
|
|
|
|
|
| |
before, we tried to be smart and wrote
an auto-generated version string via `git describe`
to alot.VERSION at setup time that got read by alot.__init__
later on.
This reverts to a hardcoded version string in alot.__version__.
It makes tedious calls to `git update-index --assume-unchanged VERSION`
unnecessary and makes life easier for packagers.
closes issue #299
|
| |
|
|
|
|
| |
actually use the version string generated by git describe
if possible. Also, don't check in every change to the version file
and let its fallback content be "0.21+"
|
| |
|
|
|
|
|
| |
and never writes it. The file /alot/VERSION
will be provided in the future and contain the
release version string. setup.py will try to overwrite this with the result of `git describe` which will suceed only if
we are on a git checkout.
|
| | |
|
| |
|
|
|
| |
http://dcreager.net/2010/02/10/setuptools-git-version-numbers/
Also makes the version string accessible as alot.__version__.
|
| | |
|
| | |
|
| |
|
|
|
| |
Read the configuration defaults from a file instead of hardcoding them in
settings.py. This also simplifies the option lookup.
|
| | |
|
| | |
|
| |
|
|
| |
issue #43
|
| | |
|
| | |
|
| |
|
