diff options
author | Sam Thursfield <sam.thursfield@codethink.co.uk> | 2015-07-14 13:27:10 +0100 |
---|---|---|
committer | Baserock Gerrit <gerrit@baserock.org> | 2015-07-28 09:46:13 +0000 |
commit | fabcc63e5dd0ad098dab3508f8c6cc78123517d0 (patch) | |
tree | 9b7f452481799a9d2cbab74638e9b32493d87598 /VERSION | |
parent | 8e4a341db6226deff45003f55afb57aa53c8fada (diff) | |
download | definitions-fabcc63e5dd0ad098dab3508f8c6cc78123517d0.tar.gz |
Add migration scripts for historical versions of the definitions format
See README for more information on how the migrations are intended work.
These migrations are probably not widely useful, as our definitions have
already been migrated manually. However, I want to come up with a good
pattern for writing migration scripts, and actually doing it seems like
the best way.
There is a 'migrations/indent' tool, which reformats a set of
definitions according to how the ruamel.yaml program writes them out.
This tool is nice if you like everything to have consistent indent and
line wrapping, and you can run it before running the migrations to
ensure that the migrations don't do any reformatting when writing the
.moprh files back to disk.
The migration scripts require the ruamel.yaml Python library. I have
sent a separate change to add this to the 'build' and 'devel' reference
systems.
Change-Id: Ibd62ba140d3f7e8e638beed6d714f671405bdc79
Diffstat (limited to 'VERSION')
0 files changed, 0 insertions, 0 deletions