nvchecker/README.rst

97 lines
3.0 KiB
ReStructuredText
Raw Normal View History

2013-05-26 14:20:14 +00:00
**nvchecker** (short for *new version checker*) is for checking if a new version of some software has been released.
nvchecker is now **in development**.
2013-05-26 15:22:21 +00:00
Dependency
==========
- Python 3
- Tornado
- All commands used in your version source files
2013-05-26 15:22:21 +00:00
Running
=======
To see available options::
./nvchecker --help
Run with one or more software version source files::
2013-05-26 15:22:21 +00:00
./nvchecker source_file_1 source_file_2 ...
2013-05-26 15:22:21 +00:00
You normally will like to specify some "version record files"; see below.
2013-05-26 15:22:21 +00:00
Version Record Files
====================
Version record files record which version of the software you know or is available. They are simple key-value pairs of ``(name, version)`` seperated by ``:`` ::
2013-05-26 15:22:21 +00:00
fcitx: 4.2.7
google-chrome: 27.0.1453.93-200836
vim: 7.3.1024
Say you've got a version record file called ``old_ver.txt`` which records all your watched software and their versions. To update it using ``nvchecker``::
2013-05-26 15:22:21 +00:00
./nvchecker --oldver old_ver.txt --newver new_ver.txt source.ini
2013-05-26 15:22:21 +00:00
Compare the two files for updates (assuming they are sorted alphabetically; files generated by ``nvchecker`` are already sorted)::
comm -13 old_ver.txt new_ver.txt
# or say that in English:
comm -13 old_ver.txt new_ver.txt | sed 's/:/ has updated to version/;s/$/./'
2013-07-03 10:23:23 +00:00
# show both old and new versions
join old_ver.txt new_ver.txt | awk '$2 != $3'
2013-05-26 15:22:21 +00:00
Version Source Files
====================
The software version source files are in ini format. *Section names* is the name of the software. Following fields are used to tell nvchecker how to determine the current version of that software.
2013-05-26 14:20:14 +00:00
See ``sample_source.ini`` for an example.
2013-05-26 14:20:14 +00:00
Search in a Webpage
-------------------
Search through a specific webpage for the version string. This type of version finding has these fields:
url
The URL of the webpage to fetch.
encoding
(*Optional*) The character encoding of the webpage, if ``latin1`` is not appropriate.
regex
A regular expression used to find the version string.
It can have zero or one capture group. The capture group or the whole match is the version string.
When multiple version strings are found, the maximum of those is chosen.
2013-07-02 09:50:45 +00:00
proxy
The HTTP proxy to use. The format is ``host:port``, e.g. ``localhost:8087``.
2013-05-26 14:20:14 +00:00
Find with a Command
-------------------
Use a shell command line to get the version. The output is striped first, so trailing newlines do not bother.
cmd
The command line to use. This will run with the system's standard shell (e.g. ``/bin/sh``).
2013-07-01 09:53:12 +00:00
Check AUR
---------
2013-07-01 10:00:58 +00:00
Check `Arch User Repository <https://aur.archlinux.org/>`_ for updates.
2013-07-01 09:53:12 +00:00
aur
The package name in AUR. If empty, use the name of software (the *section name*).
Check GitHub
------------
2013-07-01 10:00:58 +00:00
Check `GitHub <https://github.com/>`_ for updates. The version returned is in date format ``%Y%m%d``, e.g. ``20130701``.
2013-07-01 09:53:12 +00:00
github
2013-07-01 10:00:15 +00:00
The github repository, with author, e.g. ``lilydjwg/nvchecker``.
2013-07-01 09:53:12 +00:00
2013-05-26 14:20:14 +00:00
Other
-----
More to come. Send me a patch or pull request if you can't wait and have written one yourself :-)
2013-07-02 09:24:33 +00:00
Bugs
----
* Finish writing results even on Ctrl-C or other interruption.