-
Notifications
You must be signed in to change notification settings - Fork 61
Conversation
Signed-off-by: Laurent Bonnans <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm slightly amused that you ended up writing your own converter in the end, but it's really tight and looks like it should do the job, so if it works, it's fine with me. I like using the boost xml parser.
Two small things you might want to consider. We've encountered both at Foundries and have resorted to always using the repo tool to tell us the content of the manifest:
I suppose the solution to the issue I'm raising is to simply generate this file myself and then pass that to this command. However, it might make things easier for users if this command could do the dirty work for them. |
Using boost and jsoncpp Signed-off-by: Laurent Bonnans <[email protected]>
Signed-off-by: Laurent Bonnans <[email protected]>
224df36
to
4a1779e
Compare
If I understand your point correctly, this is already what we are planning to do. The input manifest is generated in this bbclass before being passed to garage-push: https://github.com/advancedtelematic/meta-updater/blob/21a463dc264434dc132ae79526a824e7955e0032/classes/image_repo_manifest.bbclass#L17. Nevertheless, I hadn't thought about a multi-manifest case. That sounds interesting and we might recommend that as well if it works as expected. |
Interesting, can you share a link or explain how that works? And is it possible to merge the manifests in some way for export, or how would you suggest keeping track of that? |
The way we manage it is like this: Each custom forks our lmp-manifes. They then create a their own "overrides" file. For example I have something like this:
To initialize my repository I then run something like: This is super handy because you can see that I can override and add things to the common platform to make it "my own". And the The huge benefit is that its pretty easy to merge our changes back into a forked repo without merge conflicts since they are doing thing in their own file. |
Codecov Report
@@ Coverage Diff @@
## master #1440 +/- ##
=========================================
Coverage ? 80.35%
=========================================
Files ? 183
Lines ? 11011
Branches ? 0
=========================================
Hits ? 8848
Misses ? 2163
Partials ? 0
Continue to review full report at Codecov.
|
Fixed formatting + small lint and added some basic exception handling. |
Cool, thanks! And as I was hoping, if |
New version of #1438, with a custom written conversion routine.