Upgrading

Warning

A reminder that compatibility for Kart 0.x releases (software or repositories) isn’t guaranteed, Kart is evolving quickly and things will change. However, we aim to provide the means to upgrade existing repositories between 0.x versions and to 1.0.*

v0.15 - Linked datasets added

Repositories created with Kart 0.15 are compatible with earlier Kart versions, unless they include “linked” datasets (which is a different way of structuring point cloud and raster datasets). Kart 0.14 and earlier cannot checkout, display or commit changes to linked datasets.

If you encounter linked datasets, simply install the latest version of Kart. You don’t need to upgrade any repositories.

v0.14 - Raster datasets added

Repositories created with Kart 0.12 are compatible with earlier Kart versions, unless they include raster datasets. Kart 0.13 and earlier cannot checkout, display or commit changes to raster datasets.

If you encounter raster datasets, simply install the latest version of Kart. You don’t need to upgrade any repositories.

v0.12 - Point cloud datasets added

Repositories created with Kart 0.12 are compatible with earlier Kart versions, unless they include point cloud datasets. Kart 0.11 and earlier cannot checkout, display or commit changes to point cloud datasets.

If you encounter point cloud datasets, simply install the latest version of Kart. You don’t need to upgrade any repositories.

v0.9 (first “Kart” release)

As of release 0.9, Sno is renamed to Kart.

Newly created repositories will have local config and structure named after kart instead of sno - for instance, a Kart repo’s objects are now hidden inside a .kart folder. Existing Sno repos using the older names will continue to be supported going forward. To modify a repo in place to use the kart based names instead of the sno ones, use kart upgrade-to-kart PATH.

Your data, changes, and branch/tag/commit histories will be preserved. Even commit hashes remain unchanged - only the local configuration is changed.

v0.8 (last “Sno” release)

As of Sno 0.8, Table Datasets V1 is no longer supported. Any repositories you have that are still using this format can still be upgraded as described in the v0.5 release, using sno upgrade /path/to/old-repo /path/to/new-repo.

v0.5

Repositories created with Sno 0.2 or higher can be used with 0.5, however some new functionality requires that you upgrade your repositories to the new format (Table Datasets V2). A future release of Sno will drop support for v1 repositories.

To upgrade your repositories to the new format, run sno upgrade /path/to/old-repo /path/to/new-repo.

Your data, changes, and branch/tag/commit histories will be preserved, along with commit dates/times/authors. Commit hashes will change.

v0.4

Repositories created with Sno 0.2 or higher are compatible with v0.4. Some command argument syntax has changed (especially init and import commands.) See the Changelog for more information.

v0.3

Repositories created with v0.2 Sno are compatible with v0.3. Some command argument syntax has changed. See the documentation for more information.

macOS

Uninstall the old version: brew uninstall sno; brew untap koordinates/sno
Install Sno v0.3 — see the Readme.

v0.2

Repositories created with older Snowdrop preview versions are not compatible with v0.2. Some command names and argument syntax have changed. See the documentation for more information.

Commit any outstanding changes to the old repositories
Uninstall the old Snowdrop software: brew uninstall --force snowdrop; brew untap koordinates/snowdrop
Install Sno v0.2 — see the Readme.
Make an empty directory for each upgraded repository (mkdir /path/to/new)
Run sno upgrade 00-02 /path/to/old-repo.sno /path/to/new {layer} where {layer} is the name of the layer in your old repository.
Your data, changes, and branch/tag/commit histories will be preserved, along with commit dates/times/authors. Commit hashes will change.