/ 
SVN-Web-0.42
River stage zero No dependents
/ UPDATING

NAME

UPDATING

SYNOPSIS

Notes on updating from previous versions of SVN::Web

DESCRIPTION

0.41 to 0.42

  • The format for specifying actions in the configuration file has changed. In addition, there are no longer any default actions -- any actions not specified in the configuration file will be ignored.

    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

  • There have been several changes to the trac templates. If you have made any local modifications then you will need to merge your changes in to the new templates.

  • Use of the 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.

0.40 to 0.41

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.

Anything < 0.40 to 0.40

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.