You may wish to place your Cava project files under a version control system. In addition to maintaining versions of your project files, this will also allow you to share the project data between different machines and operating systems.
When you start a new project, the following directory structure and files are created under the selected project folder.
../projectfolder ../projectfolder/cava20.cpkgproj ../projectfolder/cava20 ../projectfolder/cava20-logs ../projectfolder/cava20-temp ../projectfolder/installer ../projectfolder/release
For version control, you should place the file cava20.cpkgproj and the folder cava20 (and all sub-folders and files) under version control.
File and Folders included under version control
All other folders ( including all sub-folders and files) should be excluded from version control)
Folders excluded from version control
../projectfolder/cava20-logs ../projectfolder/cava20-temp ../projectfolder/installer ../projectfolder/release
These exluded folders contain files that Cava Packager will create and delete between builds and scans. None of the files are necessary to retain project information.
If you wish to maintain copies of the release folder and installer folder under version control you may wish to script your own archiving to zip or tar.gz files in some other folder that you can then place under version control.
If you use a version control system to build on different machines and operating systems, the first time you open a project after checkout or export you may have to enter some detail specific to your current machine or operating system. You will only have to do this the first time the project is opened or if you change some fundamental detail such as adding or removing executable scripts.
Details of the items that you may need to update for a new machine or operating system are covered in Project Portability.
If you use a version control system to share your project across different machines remember to update your local files from the repository before you open a project and commit to the repository when you close the project. You can't merge or resolve differences in the Cava packager binary project files if different local installations become unsynchronised.