Dave is right here.  We could add a git pull step to B2G.git/config.sh, but not 
all use config.sh to just update their tree.  Anywhere else we would update B2G 
would allow for unintended and possibly very much undesired effects.  As things 
exist today, you can already sync with just "./repo sync".

There's also the issue of automation.  It can be a surprising amount of work to 
get source from two different places in a sane way.  Doing this instead of 
improving the current two-step process also gives us branching for B2G.git 
scripts and a single source of truth about what built a given build through the 
on device manifest.

John


On Aug 11, 2014, at 10:26 AM, Dave Hylands <[email protected]> wrote:

> I think that the issue here, is that we don't have any "scripts" to do that.
> 
> What I normally do:
> 
> cd B2G
> git pull
> repo sync
> 
> But even this could have issues when not working on master.
> 
> We could create a script, and then it's an issue of problems happening when 
> the running script updates itself.
> 
> John provided some instructions for doing the entire tree setup using repo, 
> which I think means that just a repo sync would work.
> 
> Dave Hylands
> 
> 
> From: "Gervase Markham" <[email protected]>
> To: "John Ford" <[email protected]>, [email protected]
> Sent: Monday, August 11, 2014 5:16:15 AM
> Subject: Re: [b2g] Proposal: Manage B2G.git scripts in a versioned repo
> 
> wOn 05/08/14 20:51, John Ford wrote:
> > My proposal is to move nearly all of the scripts and tools in B2G.git
> > into a repo managed repository. 
> 
> I'm sure there's a reason, but why would it not be easier to have the
> scripts you run to update all the other trees first check the B2G tree
> to see whether it's outdated and, if so, stop and tell the user to
> update it first? Or even do it automatically?
> 
> Gerv
> 
> _______________________________________________
> dev-b2g mailing list
> [email protected]
> https://lists.mozilla.org/listinfo/dev-b2g
> 

_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g

Reply via email to