From: "Cole Helbling" <cole.e.helbling@outlook.com>
To: "Alyssa Ross" <hi@alyssa.is>, <devel@spectrum-os.org>
Cc: Cole Helbling <cole.e.helbling@outlook.com>, Alyssa Ross <hi@alyssa.is>
Subject: Re: [PATCH 1/2] chromiumOSPackages: improve update.py repo compat
Date: Sat, 30 May 2020 16:47:11 -0700 [thread overview]
Message-ID: <CH2PR14MB35790DDFD7A49C0BBFDBC122B38C0@CH2PR14MB3579.namprd14.prod.outlook.com> (raw)
In-Reply-To: <20200530190028.6388-1-hi@alyssa.is>
On Sat May 30, 2020 at 7:00 PM, Alyssa Ross wrote:
> These changes make chromiumOSPackages.updateScript better understand
> the Repo manifest format[1].
>
> It now properly distinguishes between paths in the Chromium OS source
> tree and paths on the git servers, which are usually not the same.
> For example, chromiumos-overlay is located in the source tree at
> src/third_party/chromiumos-overlay, but on chromium.googlesource.com
> it's located at chromiumos/overlays/chromiumos-overlays. Components
> are now keyed by their location in the Chromium OS source tree (and
> packages have all been updated for this change.)
>
> Additionally, it now understands Repo remotes. This means that it is
> now possible to use a Chromium OS component like Minijail, which is
> hosted on android.googlesource.com rather than
> chromiumos.googlesource.com. This was not previously possible.
>
> [1]:
> https://gerrit.googlesource.com/git-repo/+/HEAD/docs/manifest-format.md
> ---
> .../linux/chromium-os/common-mk/default.nix | 2 +-
> .../linux/chromium-os/crosvm/default.nix | 4 +-
> .../os-specific/linux/chromium-os/default.nix | 2 +-
> .../linux/chromium-os/libqmi/default.nix | 2 +-
> .../linux/chromium-os/minigbm/default.nix | 2 +-
> .../linux/chromium-os/modem-manager/next.nix | 2 +-
> .../linux/chromium-os/modp_b64/default.nix | 2 +-
> pkgs/os-specific/linux/chromium-os/update.py | 56 ++++++++++++-------
> .../linux/chromium-os/upstream-info.json | 40 ++++++-------
> pkgs/os-specific/linux/kernel/linux-cros.nix | 2 +-
> 10 files changed, 64 insertions(+), 50 deletions(-)
Hopefully this means next time I can fulfill my promise of helping
out... Fingers crossed Google doesn't change/break anything between now
and then.
Reviewed-by: Cole Helbling <cole.e.helbling@outlook.com>
next prev parent reply other threads:[~2020-05-30 23:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-30 19:00 Alyssa Ross
2020-05-30 19:00 ` [PATCH 2/2] chromiumOSPackages: 81.12871.0.0-rc1 -> 83.13020.0.0-rc1 Alyssa Ross
2020-05-31 3:01 ` [PATCH v2 " Alyssa Ross
2020-05-31 23:49 ` Cole Helbling
2020-06-01 22:44 ` Alyssa Ross
2020-06-01 23:00 ` Alyssa Ross
2020-06-01 23:38 ` Michael Raskin
2020-06-01 23:55 ` Alyssa Ross
2020-06-02 0:37 ` [PATCH platform2] vm_tools: proto: fix parallel build Alyssa Ross
2020-06-02 0:39 ` Cole Helbling
2020-06-02 0:56 ` [PATCH v3 2/2] chromiumOSPackages: 81.12871.0.0-rc1 -> 83.13020.0.0-rc1 Alyssa Ross
2020-06-02 2:27 ` Cole Helbling
2020-06-02 3:19 ` Alyssa Ross
2020-06-02 8:39 ` [PATCH v3 2/2] chromiumOSPackages: 81.12871.0.0-rc1 ->83.13020.0.0-rc1 Michael Raskin
2020-05-30 23:47 ` Cole Helbling [this message]
2020-06-02 3:30 ` [PATCH 1/2] chromiumOSPackages: improve update.py repo compat Alyssa Ross
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CH2PR14MB35790DDFD7A49C0BBFDBC122B38C0@CH2PR14MB3579.namprd14.prod.outlook.com \
--to=cole.e.helbling@outlook.com \
--cc=devel@spectrum-os.org \
--cc=hi@alyssa.is \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://spectrum-os.org/git/crosvm
https://spectrum-os.org/git/doc
https://spectrum-os.org/git/mktuntap
https://spectrum-os.org/git/nixpkgs
https://spectrum-os.org/git/spectrum
https://spectrum-os.org/git/ucspi-vsock
https://spectrum-os.org/git/www
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).