UPDATING
Notes on updating from previous versions of SVN::Web
If you have not modified the supplied template files the update can be carried out by:
svnweb directory.svnweb-install from this distribution.
This will copy the new templates,
as well as creating a new config.yaml.If you have made local modifications then the following information should help you merge the changes in this version in to your modified files.
version key in your configuration file to 0.53.[% path | uri | html %]
in a template, now you can just write
[% path %]
If you do not re-run svnweb-install when you upgrade to this version you must update the templates by hand.
version key in your configuration file to 0.52.version key in your configuration file to 0.51.version key, the value of which must match the SVN::Web version. If it is not present, or does not match, SVN::Web will die(), and generate an appropriate error in the logs.
Add this line:
version: 0.50
to config.yaml, after making sure that you have updated the configuration file to contain all the necessary new directives.
svnweb-install, as advised above, or view the documentation for each action, which has been updated to show the new entries that should be placed in config.yaml for the action.
This change has also affected all the action templates save for list and rss. There is a new Template/trac/_action_menu template.
The diffs are:
In addition, there is a new trac/rss template, and a new Style/trac/feed-icon-16x16.png, both of which must be copied in to place.
at_head variable. The revision with the change is http://jc.ngo.org.uk/svnweb/jc/revision/?rev=871.This was a bug fix release, with no changes to the templates, localisation, or configuration files.
This was a bug fix release, with no changes to the templates, localisation, or configuration files.
If you have not modified the supplied templates and localisation files the update can be carried out by:
svnweb directory.svnweb-install from this distribution. This will copy the new templates and localisation files, as well as creating a new config.yaml.If you have made local modifications then the following information should help you merge the changes in this version in to your modified files.
The diff for these changes is at http://jc.ngo.org.uk/svnweb/jc/revision/?rev=793.
The diff for these changes is at http://jc.ngo.org.uk/svnweb/jc/diff/nik/CPAN/SVN-Web/trunk/lib/SVN/Web/I18N/en.po?revs=794&revs=788.
The diffs for these changes are at http://jc.ngo.org.uk/svnweb/jc/diff/nik/CPAN/SVN-Web/trunk/lib/SVN/Web/I18N/en.po?revs=788&revs=719 and http://jc.ngo.org.uk/svnweb/jc/diff/nik/CPAN/SVN-Web/trunk/lib/SVN/Web/Template/trac/browse?revs=788&revs=553.
The diff for these changes is at http://jc.ngo.org.uk/svnweb/jc/revision/?rev=719.
The diff for this change is at http://jc.ngo.org.uk/svnweb/jc/revision?rev=721.
svnweb-server quiet. It's not essential that you update your copies accordingly, but it doesn't hurt either.
The diff for this change is at http://jc.ngo.org.uk/svnweb/jc/revision?rev=764.
To retain existing functionality you must ensure that the following appears in config.yaml.
actions:
browse:
class: SVN::Web::Browse
checkout:
class: SVN::Web::Checkout
diff:
class: SVN::Web::Diff
list:
class: SVN::Web::List
log:
class: SVN::Web::Log
revision:
class: SVN::Web::Revision
rss:
class: SVN::Web::RSS
view:
class: SVN::Web::View
templatedir configuration directive is now deprecated. You should use templatedirs instead. This is to support third party actions that supply their own templates in different directories.
templatedir in the configuration file will continue to work, but you should change existing entries of the form:
templatedir: '/path/to/directory'
to this form:
templatedirs:
- '/path/to/directory'
A configuration file that specifies both templatedir and templatedirs will generate an exception when anyone browses the repository.
After installing the new module you should copy lib/Templates/trac/header to <dir>/template/trac/header, where <dir> is the directory in which you ran svnweb-install.
The 0.40 release includes sweeping changes to the templates, as well as additional functionality and configuration directives. See CHANGES for details.
The simplest approach is to backup your existing config.yaml and then re-run svnweb-install. This will generate a new config.yaml and copy over the new templates and other files.
It should be easy to migrate your old configuration directives to the new configuration file.
