#1. Do not delete anything, especially not .repo! If you have made changes in your working tree you might want to reset those. Sometimes files are created in your working tree during configuration or build, but then your config run will complain and tell you which directory has changes. Deleting that directory in your working tree is safe. Run *./repo status* to see any stray files.
#2 No, it essentially runs *git fetch* for all repos listed in the manifest. See more info further down. #3 You shouldn't use git to just update your code base. When you run *./config.sh*, it will setup the manifest for the device you gave it. It will then essentially run *./repo sync *with the options you provided to config.sh (for instance, -l will only use local files, hence not update any repos over the network). The repos are stored in *.repo/projects* but that folder should not be touched at all. *./repo*will handle everything for you. When you run *./config.sh* or *./repo sync*, only the necessary files will be downloaded. That is, if you have already downloaded the necessary repos, you will only be fetching commits and branches that were added after your previous sync. So in short, If you are not changing to another device, you only need to run *./repo sync* to update to the latest and greatest. If you want to switch to another device fast (not check each repo for new stuff, for instance when you know you updated for that device recently) you should run *./config.sh -l <device>*. Also note that when building for different devices, the resulting binaries and libraries will live in different places (under *out/target/product*), so there is no need to clear any old stuff out when building for a new device. *Andreas Pehrson *--- Software Engineer (+47) 959 60 374 | [email protected] | www.comoyo.com On Fri, Jan 17, 2014 at 4:58 PM, Techno Buddha <[email protected]> wrote: > Hi all, > So I'm now suffering with having to pay an extra $50 for my Bell > downloads, as I went over my limit without checking! My problem I know. LOL! > > I realized that building for a device will force down all of the > components to build, hence the 7G of data each time. And well I've > downloaded it all about 6 or 7 times. LOL! So, I'm reading up on GIT, and > trying to figure out with the shell scripts config and repo, and build, and > i'm hoping someone can point me to some advice with regards to using b2g > git? > > I will be using several different devices to test with, and I NOW know > that you don't have to download everything all over again, that the items > that will be downloaded will be in the manifest, correct? > > #1 to go from one device to another, do you just delete the "build" and > the .repo (excluding the downloaded files) directory, and change the > manifest to the right one? (most likely with the config file) is there a > specific command? > > #2 if you do the config, is everything downloaded all over again, even if > it already exists? or could we just find out the difference in the manifest > file and use git to down load that part? > > #3 what git command should I use to downloaded the latest changes, and > ignore? the current files created? > > Please forgive my ignorance, as I'm a systems guy trying to dive into the > development world so I can better support developers, and I think the best > way to do that is to focus on the new firefox OS! > > I'm also going to read up a bit more on GIT, so if anyone can point me to > relivent info so i can get up to speed quicker? > > and one last question? what's the most cheapest phone to buy (used) that > works with firefox os? > > thank you! > _______________________________________________ > 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
