#SVN KEYWORD HOW TO#
#SVN KEYWORD UPDATE#

It is designed to have various (pluggable) output formats, so that you can make your build script as simple as:Д«zrВ version-infoВ -allВ -format=pythonВ >В version.py Oh, and if you want to do this sort of thing the same way I do, you might look at the 'version-info' command.I'm putting together a plugin for this to test out the workingtree content filtering feature.I believe there should be local default, versioned property and local override.

#SVN KEYWORD HOW TO#

One issue to solve is, how to specify which filters to use for a particular file.

That would also take care of keyword expansion. In LineEndings I suggested, that plugable filters for file contents should exist.

#SVN KEYWORD UPDATE#

commit, pull) must update all keyword files.

Anything that alters Branch.last_revision() results (e.g.

Consideration of how this will interact with hashcache.

Expand and unexpand methods in the workingtree object.

Require per-file versioned properties (like svn) to record whether expansion should be on or off for a particular file.ДЄll access to the working file should be through the WorkingTree class.

get only the version into a string without the dollar signs. PRCS has a nice system for doing the expansion on the line following the keyword, which helps when you can to e.g. Expansion should be off by default, and optionally turned on per file. We wish to support expansion of $Id$ style keywords, as used in cvs and svn.

keyword values are lazily evaluated so there is limited impact on performance and you only 'pay' for the keywords you use.Дesign notes and comments leading to the development of this plugin are shown below.

other plugins can register additional keywords.

to assist those working with multiple VCS tools on the one tree, unknown keywords are still stored in compressed form during a commit and their expanded value is left unchanged in the working tree.

Keywords are optionally expanded by bzr cat and bzr export including various publishing styles that drop the $ markers to improve readability

users can configure how they want date-time keyword values formatted by adding settings to nf.

keywords supported include: Date, Author, Author-Email, Revision-Id, Path, Filename, Directory, File-Id, Now, User, User-Email.

enabled per file pattern in selected branches via rulesДЇor different patterns, keywords can be set to off, on and xml_escape, the latter providing escaping of values for inclusion into XML and HTML files.

Please help test this plugin so we can maximise its usefulness and quality. As explained on that page, the plugin requires a branch supporting content-filtering, a feature planned for inclusion in a future version of Bazaar. A plugin implementing this feature is now available for testing.

Svn keyword