Build a specific branch

[Sonny Sasaka]

Hi Chromium OS Ninjas,

I am trying to build Chrome OS for a specific version (i.e. 9064.0.0). However I can't find that branch name in the repo (I was looking for stabilize-9064). Is there a way to build this specific version? Thank you!

[Bernie Thompson]

Chrome OS does not have a branch for every version, we only make branches where we need to release a sub version (e.g. 9064.1.0).

However we do save manifests for every version so you should be able to recreate it, the manifests are all stored in https://chrome-internal.googlesource.com/chromeos/manifest-versions/ where you should be able to find a manifest file for your particular version that specifies the git hashes that were used in the build.

If you pull one of these manifest files, you should be able to point repo at it with -m and get a set of sources that match what that version had. 

-Bernie

On Thu, Jun 15, 2017 at 3:00 PM, Sonny Sasaka <sonny...@chromium.org> wrote:

Hi Chromium OS Ninjas,

I am trying to build Chrome OS for a specific version (i.e. 9064.0.0). However I can't find that branch name in the repo (I was looking for stabilize-9064). Is there a way to build this specific version? Thank you!

--
--
Chromium OS Developers mailing list: chromiu...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-os-dev?hl=en

[Sonny Sasaka]

Thanks, Bernie. I will try that.

[Sonny Sasaka]

I am able to checkout the code using that manifest. Now I am wondering whether ./build_packages will build Chrome or will use an existing Chrome binary.

Is there a way to specify build_packages to use a pre-built Chrome binary?

[Mike Frysinger]

build_packages by default should use binary packages.  when it prints the summary, just look at the lines for "[ebuild" vs "[binary" at the start.

-mike

[Sonny Sasaka]

Got it. Thanks, Mike!