path: root/migrations
Commit message (Collapse)AuthorAgeFilesLines
* Firehose test commitFirehose merge bot2015-09-282-5/+32
* Fix issues in the initial DEFAULTS file and version 7 migration scriptSam Thursfield2015-09-222-184/+205
| | | | | | | | | | | | | | | | | | | | | | | | | | First, embedding it in the Python script was stupid as \ characters got mangled, it's now in a separate file. The strip commands were totally broken, causing certain builds to fail, which is fixed now. The default commands for the 'cpan' build system are now in line with those built into Morph. The 'autotools' commands have been tweaked too, so that now they produce identical cache keys to the defaults that are built into Morph (as of morph.git commit 07df32fbd57477e5808cdbace965edcd0a81348f). This means that moving to definitions format version 7 should not trigger any rebuilds of anything. Also, I added the 'module-build' build system (which was added to Morph in commit f6613fe1ee6d879192fd4e503cb632b0dcab1fe7), so that it can be used in the reference systems once they use definitions format version 7. The migration script will warn if the definitions are version 7 already but there is no DEFAULTS file, because that's unlikely to be deliberate. Change-Id: I0a739ef38f521530e0d86d7330d1bcecf0a5bb73
* Add migration and schema for definitions version 7Sam Thursfield2015-08-251-0/+243
| | | | | | | | | Version 7 of the schema adds a new file called DEFAULTS. I thought the best way to describe the layout of this file was to add a JSON-Schema description of it, and I propose keeping the canonical version of it in this Git repository in the schemas/ subdirectory. Change-Id: I18b6b997ba4e9f34028b98ccf682bdf56e507cec
* Set migrations/ to be executableSam Thursfield2015-07-291-0/+0
| | | | This was an oversight in the previous commit.
* Add migration for definitions version 6Sam Thursfield2015-07-281-0/+329
| | | | Change-Id: I80ce9eee253b25689f9a360047dc9b3e9b1cb12a
* migrations: Don't run 'indent' as a migrationSam Thursfield2015-07-281-1/+2
* Add migration scripts for historical versions of the definitions formatSam Thursfield2015-07-2810-0/+801
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