NAME

UPDATING

SYNOPSIS

Notes on updating from previous versions of SVN::Web

DESCRIPTION

If you have not modified the supplied templates and localisation files the update can be carried out by:

  1. Backing up your existing config.yaml file.

  2. Removing all the files in your current svnweb directory.

  3. Running svnweb-install from this distribution. This will copy the new templates and localisation files, as well as creating a new config.yaml.

  4. Restoring the config.yaml that you backed up in step 1, and making any changes, as described below.

If you have made local modifications then the following information should help you merge the changes in this version in to your modified files.

0.47 to 0.48

0.46 to 0.47

0.45 to 0.46

This was a bug fix release, with no changes to the templates, localisation, or configuration files.

0.44 to 0.45

This was a bug fix release, with no changes to the templates, localisation, or configuration files.

0.43 to 0.44

If you have not modified the supplied templates and localisation files the update can be carried out by:

  1. Backing up your existing config.yaml file.

  2. Removing all the files in your current svnweb directory.

  3. Running svnweb-install from this distribution. This will copy the new templates and localisation files, as well as creating a new config.yaml.

  4. Restoring the config.yaml that you backed up in step 1.

If you have made local modifications then the following information should help you merge the changes in this version in to your modified files.

0.42 to 0.43

  • The en.po localisation file and diff template have been changed to support viewing plain text diffs. Either copy the supplied files over your copies, or merge the changes in by hand if you are using your own templates.

    The diff for these changes is at http://jc.ngo.org.uk/svnweb/jc/revision/?rev=719.

  • SVN::Web::Revision has a new option controlling whether or not diffs are shown when viewing a revision. To support it the revision template has changed. Either copy the supplied template over your copy, or merge the changes by hand if you are using your own template.

    The diff for this change is at http://jc.ngo.org.uk/svnweb/jc/revision?rev=721.

  • The templates trac/trac.css and trac/code.css have been changed to remove references to images that are not shipped in this distribution. This will stop web browsers requesting them, and keeps 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.

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.