Package standalone compressed binaries (7z format)

[ghost]

It would be handy for testing and feature comparison (possibly other things) if we could package a standalone compressed file along with our other packages. CPack should allow us to do that. I would be interested in any feedback on this.

[Krzmbrzl]

Isn't the issue on Windows that e.g. shortcuts only work if the Mumble executable is located in the programs directory?

Plus we have the issue of settings and the like (database) being stored globally and therefore we could end up having conflicts there between different versions.

[Krzmbrzl]

Shortcuts are not necessary as you would run it directly from the resulting folder.

That depends on the use-case. If you want to test something shortcut-related then this is actually very important ^^

I don't think a newer version adding entries that an older version doesn't query should be an issue unless something isn't right.

Adding new entries is probably not an issue, no. But settings being removed or the content format of any setting changing would be a (huge) issue.

It should be a practice to back up the config in case of such issues when testing, anyway.

On Linux (and Mac?) this is very easy but on Windows it is (I think) more tedious as you have to extract and re-insert keys from the registry...

[ghost]

I see your points. It would be difficult even if we unify the config structure unless we add checks for the configs in the root of the binary folder as well as places like %appdata%\mumble. At the very least, it might be a good idea to discover if the registry is the best and only way to handle config items.

[davidebeatrici]

It's not unusual to see portable applications using a .reg file as storage instead of the system's registry, however it's generally done when said applications are not officially portable.

Using a configuration file on Windows as well is the way to go in my opinion.
As for backwards compatibility, we can simply check whether the configuration file already exists.
If it doesn't, we check whether the settings were saved in the registry and eventually import them.

[Krzmbrzl]

Using a configuration file on Windows as well is the way to go in my opinion.

Agreed. We'd have to do that in any case if we want a uniform way of storing settings across OS.

[davidebeatrici]

Indeed.

[gitgrub]

+1 for client config in an ini file.
That would be nice to just unzip and testing, without installation.