Re: Extensible workspaces.yaml format



Hi Daniel,

On 05/12/17 14:28, Daniel Playle wrote:
To assist with parsing the proposed format, a version attribute is
introduced, allowing a new parser of the `workspaces.yaml` file to
accept both formats, thereby not breaking any existing workspaces when
a user upgrades to BuildStream using the proposed format.

Current Format:
```
alpha.bst:
   0: /workspaces/bravo
   1: /workspaces/charlie
```

Proposed Format:
```
version: 1
build-elements:
   alpha.bst:
     sources:
       0:
         path: /workspaces/bravo
       1:
         path: /workspaces/charlie
```

I'd like to know if this proposal is something that the community
thinks would be valuable?

I like the idea of the version attribute, and also other the proposed changes look sensible as they make it easier to add more information in a backwards-compatible way.

There's a question of how long we support each version in the code, but I guess 2 parallel versions isn't too bad.

So i'd be in favour of this, although to me it makes sense to wait until we actually need the new version (for example when Chandan's incremental-builds branch is merged) to make the change.

Sam

--
Sam Thursfield, Codethink Ltd.
Office telephone: +44 161 236 5575


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]