Relative paths for audio files

[mjomble]

Splitting off from this thread: http://www.adventuregamestudio.co.uk/yabb/index.php?topic=44230.0

But now I've got a second, smaller submission: when you add a new audio file to your project and the file is within your game directory, store only the relative path and not the full absolute path.
This has been a major pain for our project because we share the project files between different members of the team (and sometimes between multiple computers of one member) via SVN and the absolute paths are different on almost every machine.

The secondary issue I guess would only be a problem if multiple people are trying to modify the sound files? Otherwise I'm not sure I understand the issue. The audio cache is automatically updated if the source file exists and is changed, so you're saying that the source file (within the project folder) may need to be modified by one of the members of your team, but if they don't have their copy of the project in the same path as the person who originally added the audio file then it's not automatically updated? This change sounds reasonable to me, though it wouldn't really be too hard to just delete the file and reimport it.

Ideally, we'd like to exclude AudioCache from the repository and only share the original files.
Not only does it feel cleaner, it also keeps the repository smaller and updates/commits faster if there are large audio files.

The fact that the paths are absolute forces us to choose between the following options:

1. Keep both AudioCache and the original audio files in version control.
Every change needs to be uploaded/downloaded twice because of the data duplication.
If an audio file is updated by someone whose absolute path is at the moment different from the original upload's, the update won't make it to the cache until someone with the original path runs AGS, saves the project and commits the AudioCache changes.

2. Keep only AudioCache files in version control.
This takes care of the duplication, but difficult to maintain (and not really designed to be maintained by the user in the first place).

3. Keep only the original files and convert the absolute paths to relative ones by editing Game.agf externally.
This is the solution that currently works for us, but is rather annoying to maintain and we often forget to do the cleanup. It could easily be automated by the editor with a simple change.