summaryrefslogtreecommitdiff
path: root/README
Commit message (Collapse)AuthorAgeFilesLines
* Add schemas for Baserock definitions formatSam Thursfield2015-09-181-2/+2
| | | | | | See schemas/README.schemas for information. Change-Id: I6c384692dbf70017a3ece2ed56c1f8cbe60b493d
* Add migration scripts for historical versions of the definitions formatSam Thursfield2015-07-281-4/+48
| | | | | | | | | | | | | | | | | | | | | | 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
* README: explain what it means for a system definition to be on systems/Javier Jardón2015-06-101-0/+6
| | | | | Thanks to Marc Dunford for the bug report Change-Id: Ie9d1545f766bca93979a576085896cf9af1006bf
* Update README to be slightly more explanatoryLars Wirzenius2013-07-221-1/+3
| | | | Suggested-by: Tiago Gomes
* initialLars Wirzenius2011-10-081-0/+4