Merge lp:~cjwatson/launchpad/db-snappy into lp:launchpad/db-devel
Proposed by
Colin Watson
on 2015-07-20
| Status: | Merged | ||||
|---|---|---|---|---|---|
| Merged at revision: | 13160 | ||||
| Proposed branch: | lp:~cjwatson/launchpad/db-snappy | ||||
| Merge into: | lp:launchpad/db-devel | ||||
| Diff against target: |
216 lines (+159/-0) 2 files modified
database/schema/patch-2209-69-0.sql (+140/-0) database/schema/security.cfg (+19/-0) |
||||
| To merge this branch: | bzr merge lp:~cjwatson/launchpad/db-snappy | ||||
| Related bugs: |
|
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| William Grant | db | 2015-07-20 | Approve on 2015-07-30 |
|
Review via email:
|
|||
Commit Message
Add Snap, SnapArch, SnapBuild, and SnapFile tables.
Description of the Change
Add Snap, SnapArch, SnapBuild, and SnapFile tables.
This is basically LiveFS with the serial numbers filed off, although instead of having a metadata dict we take a Branch/GitRef and expect that to contain the snapcraft recipe. I initially went for a recipe text column containing YAML, but following discussion with the snapcraft team a version control branch seems to be the most sensible way to pass the recipe, not least because there may need to be some other snap-specific metadata other than snapcraft.yaml and so one will often want a container for that anyway.
To post a comment you must log in.
review:
Approve
(db)
