1

Fuchsia > Guides -- Get Fuchsia source code seems to imply that git is involved in the downloading of the source for Fuchsia OS: 

$ sudo apt-get install build-essential curl git python unzip

The actual commands for the download do not use git explicitly:

curl -s "https://fuchsia.googlesource.com/fuchsia/+/master/scripts/bootstrap?format=TEXT" | base64 --decode | bash

Fuchsia > Guides -- Contribute changes show a git command as the first step in the process of making a coding change to Fuchsia OS.

git checkout -b <branch_name>

What is the relationship of getting the source for a build from fuchsia.dev and the process to submit a change to fuchsia.googlesource.com?

For example, does one need to do these as two separate actions to different places or can one just jump in the middle of the downloaded sources from fuchsia.dev for the git commands as described in fuchsia.googlesource.com?

CW Holeman II
  • 4,661
  • 7
  • 41
  • 72

1 Answers1

1

Fuchsia uses a tool called jiri to manage the multiple repositories that make up a complete Fuchsia build/development environment. You'll see that the boostrap script mentioned in your post makes use of this tool to do the checkout.

After jiri is done making your environment for you, you can use git commands as per usual. jiri is just the tool used to make sure you have a consistent/working set across the multiple git repositories in the project.

What is the relationship of getting the source for a build from fuchsia.dev and the process to submit a change to fuchsia.googlesource.com?

Getting a development environment is best done with the jiri tool. You'll end up with a bunch of git repositories to which you can make changes. Those changes can be pushed via normal git/gerrit commands to submit code for review.

For example, does one need to do these as two separate actions to different places or can one just jump in the middle of the downloaded sources from fuchsia.dev for the git commands as described in fuchsia.googlesource.com?

The git repositories cloned by the jiri tool are suitable for doing development and pushing code for review. Their origin remotes should be correctly set up "out of the box" so to speak.

Carl Norum
  • 219,201
  • 40
  • 422
  • 469
  • The git checkout is step 1 of 5. At which step & how should the identity of the one making the change handled? – CW Holeman II Mar 15 '20 at 10:18
  • Your information is associated with the commit as it would normally be with any git commit. If you don't have anything set globally, git will walk you through how to set that up. All you should need are to have `user.name` and `user.email` set in your git config (either for the project or globally). – Carl Norum Mar 15 '20 at 21:59
  • I guess that's step 4 [here](https://fuchsia.dev/fuchsia-src/development/source_code/contribute_changes#create-a-change-in-gerrit). – Carl Norum Mar 15 '20 at 22:01
  • Edit rolled back for some weird stuff in the middle. Will take a closer look soon. – Carl Norum Mar 16 '20 at 22:16