Should the need arise, it is possible to install two or more versions of CrossOver side-by-side so they don't interfere. When this happens, each installation tags its resources with a 'product id', so it knows which desktop menus and associations belong to it.
When using the graphical installer all you need to do is pick a new installation directory. The installer will then notify you that another version of CrossOver is already installed elsewhere, and if you proceed it will automatically pick a new product id to avoid interference.
When upgrading a side-by-side configuration using the graphical installer, always double-check the installation directory to make sure you are upgrading the CrossOver instance you intended to.
It is also possible to set up side-by-side configurations using Debian or RPM packages. But to do so you must first repackage CrossOver to change the package name and the product id.
To do so you must first install the CrossOver version to repackage. You would typically do this in a user account using the graphical installer as this avoids interference with already installed packages. Then run the following command in that account:
cxnew is both the new package name and the
new product id, and
2 lets you keep track of the
revisions of the new packages you create. To generate an RPM package instead
of a Debian one, simply replace
To create Debian or RPM packages you will need your Linux distribution's corresponding packaging tools.
The new package can then be installed and deployed normally, next to the regular CrossOver package. You can also use it to create bottle packages that will work together with your new package instead of the regular ones.