Release exporter should generate scripts that works with the "update" importer mode

[Nicklas Nordborg]

The "update" mode in the release importer is described in Relax ticket #1095 and works by only updating annotations for items that are already existing and part of an existing release (=project).

The scripts that are created by the release exporter need similar functionality. Basically:

• The mkdirs.sh script should only create directories if they also already exists in another release directory. This other directory should be specified as a parameter. If no other directory is specified, a full directory structure is created.
• The mklinks.sh script should only create links if they also already exists in another release directory (as a link or file). This other directory should be specified as a parameter. If no other directory is specified, all links are created.
• The rsync.sh script is not needed in "update" mode so no changes are required.

[Nicklas Nordborg]

(In [5193]) References #1098: Release exporter should generate scripts that works with the "update" importer mode

New scripts are now created. The mkdirs.sh and mklinks.sh scripts now has support for specifying a second parameter that should be the path to the top-level directory of an existing release. Examples:

# Create a full release
./mkdirs.sh
./mklinks.sh
./rsync.sh

# Create release 1.1 as an update to 1.0
# No rsync in this case
./mkdirs.sh ../1.1 ../1.0
./mklinks.sh ../1.1 ../1.0

[Nicklas Nordborg]

(In [5196]) References #1098: Release exporter should generate scripts that works with the "update" importer mode

The rsync.sh script had abug due to an incorrectly named variable.

The README has been updated with more information and examples.

[Nicklas Nordborg]

(In [5248]) References #1098: Release exporter should generate scripts that works with the "update" importer mode

Improved status reporting in the release scripts.