Releases: alebcay/cooler
Releases · alebcay/cooler
v0,7,4
v0.7.3
v0.7.2
v0.7.1
v0.7.0
New Features
- Added support for the Unix settings export software Mackup
- Addresses lra/mackup#223
- Include your application settings in your Cooler bundle with the
--mackup
flag on export, and apply the settings with the flag on import - Using
--mackup
will make your bundles a lot bigger, so use this feature wisely
- Using LZMA compression instead of GZip
- Slightly better for dealing with the insane file sizes that Mackup pumps in (not much that can be done about it though)
- ALL PREVIOUS COOLER BUNDLES CREATED WITH PREVIOUS COOLER VERSIONS ARE NOW INCOMPATIBLE!
v0.6.0
v0.5.1
v0.5.0
New Features
list
command now lists the contents of a Cooler bundle- Cooler now accepts the bundle name argument as a path to the bundle, NOT the name of the bundle (e.g. you should now provide
cooler import /foo/bar/bundle.cb
instead ofcooler import /foo/bar/bundle
). This allows users to use their own file extensions, for whatever reasons- Old cooler bundles are still compatible, new bundles created are still backwards-compatible
v0.4.9
v0.4.8
New Features
- Export function now tells you where the finished bundle is located
Bug Fixes
- Import and export now working for bundles that aren't in the current working directory.
- For example, the following would not have worked before, but is now functioning properly:
cooler export /some_other_dir_path/myExportBundleName
andcooler import /some_other_dir_path/myExportBundleName
- For example, the following would not have worked before, but is now functioning properly:
Known Issues
- Errors given if user does not have write access to the location where a bundle is stored (or where one will be made)