| commit | 57fddcbbee7d94fedd9b397baa0957edb968f676 | [log] [tgz] |
|---|---|---|
| author | Hunter Freyer <hjfreyer@fuchsia.infra.roller.google.com> | Wed Mar 06 00:34:20 2024 +0000 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Mar 05 16:36:13 2024 -0800 |
| tree | 5f4e18d210e5ff6f167cf478bfb7497a0d8b3133 | |
| parent | 14ea51bb95b5832b1fb9519af05768c3a516aee0 [diff] |
[roll] Roll fuchsia [package-tool] Support api-level=HEAD. More generally, this adds support for the mutable "pseudo-API-levels" HEAD, LEGACY, and eventually NEXT. The ABI revision and status assigned to these API levels is not correct - it should use a random "per release" ABI revision (see fxbug.dev/42082683). But, we're getting there one step at a time. We first need to make sure that everyone actually specifies which API Level they're targeting, always. This also changes the platform build to specify `LEGACY` while building the platform, and a specific API level in IDK subbuilds. The fact that the addition of these API levels is implemented in `parse_version_history` is perhaps a bit strange. It could come earlier, with `HEAD` and `LEGACY` actually appearing in `version_history.json`, but the ABI revision will eventually be dynamically generated, so they'd still need to be treated specially there. They could also be added later, but then every method in VersionHistory would need to treat them specially, since they wouldn't appear in the constant. We may need to reconsider this, especially as we explore what it means for SDKs to support targeting `NEXT` and `HEAD`, but I think this will do for now. Also make the error messages marginally prettier. Original-Fixed: 327656572 Original-Bug: 327657448 Original-Fixed: 326655565 Original-Bug: 305961460 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/998738 Original-Revision: bd01bb500f9d14d3ba8841d7aa4fca692bb24163 GitOrigin-RevId: 9e98ccaa6d09cee43cc36b503656b9f8c8283514 Change-Id: I29f1e8ccd8507f4948ffbce30bbe59e6cb4d77fb
This repository contains Fuchsia's Global Integration manifest files.
All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.
Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.