search

GatorQue / git-repo-flow

Enhanced Google repo alternative that utilizes a git-flow methodology.
Apache License 2.0
6 stars 3 forks source link

Flow elements are not preserved during manifest xml save #10

Closed GatorQue closed 8 years ago

GatorQue commented 8 years ago

Need to add the ability to save the <flow> elements during a manifest save operation. Internally, it should be possible to detect when the <flow> elements should be saved in <project> element or the <remote> element by comparing the project.flow and project.remote.flow values. If they are identical, then the <flow> element belongs at the <remote> level. If both exist, but are not identical, then it belongs in both the <project> and <remote> elements (project override case). If project.remote.flow doesn't exist, then it should only be at the <project> level. The above should only be done if peg to revision is not enabled.

GatorQue commented 8 years ago

Now implemented, see commit hash: 1169b5f220ea5e74954d8e1950fa9ab8995b27e6.

smipi1 commented 8 years ago

@GatorQue,

Have a look at the python tool written to modify manifests in the BSB002 platform project. It will be in build/bsb002/tools/manifest or make/tools. It preserves the xml structure as well as possible by using lxml.

On Fri, 5 Feb 2016, 03:32 Ryan Lindeman notifications@github.com wrote:

Closed #10 https://github.com/GatorQue/git-repo-flow/issues/10.

— Reply to this email directly or view it on GitHub https://github.com/GatorQue/git-repo-flow/issues/10#event-540124740.