tha.taglist 0.6.1

Create find-links list of tags

Taglist generator for findlinks

tha.taglist generates an html list of svn tags suitable for zc.buildout’s find-links.

Installation

Installation is the normal buildout procedure.

How it works

The script iterates over the BASE repository as defined in tha/taglist/defaults.py. It first tries to use BASE_ON_SERVER, which you can use to define file:///svn as an alternative base when available, which speeds it up on the server and which also makes it usable for every user account. It has a blacklist of directories it won’t interate into. Every directory is examined for “stop indicators” like setup.py that indicate that there aren’t any useful tag directories further down. See defaults.py for documentation on how to override it in your buildout.

If a tags/ directory is found an entry in the packages.html is added with:

• The tag (‘1.0’). We do a regex search for the version in the setup.py. If found and if it doesn’t match the tag, we emit a warning.

• The svn url.

• The name that is extracted (with a regex) from the setup.py.

You can start the script with ‘-v’ or ‘-vv’ for more verbose logging.

Changelog for tha.taglist

0.6.1 (2009-02-26)

• Doc update. [reinout]

0.6 (2009-02-26)

• Configuration is now done through a defaults file that can be overridden by a buildout option. [reinout]

0.5 (2009-02-26)

• Added generation date to the top of the generated html file. [reinout]

• Quieted down logging to only emit warnings. Added -v and –v options for info/debug level logging. [reinout]

• Added check (regex-based) whether the version in setup.py matches the tag. If not, it emits a warning. [reinout]

0.3 (2009-02-25)

• Added TODO.txt

• Make destination configurable.

0.2 (2009-02-25)

• Using file:///svn on server (with non-server fallback to svn+ssh). [reinout]

0.1 (2009-02-25)

• Added buildout.cfg. [reinout]

• Tags are searched in the entire tree (excluding blacklisted items). [reinout]

• The html gets written to generated.html. [reinout]

• Extracting name from setup.py with a regular expression. [reinout]

TODO

• Option: check the name and version for each tagged package by finding the setup.py, running it and asking for its name and version instead of doing a regex search. For this you need a full checkout of the whole repository instead of just a temporary checkout of a setup.py file.