[roll] Roll fuchsia [idk] Do not expose `content_checklist_path` file in packages' metadata
These files are implementation details of the IDK build process (they
are used to verify that the package includes required files), but there
is no good reason to have them listed in the `variants.files` list of
an SDK package's `meta.json` file.
In other words:
```
{
"name": "foo",
"type": "package",
"variants": [
{
"api_level": 19,
"arch": "x64",
"files": [
"packages/blobs/...",
...
"packages/foo/x64-api-19/release/content_checklist_path", <== REMOVED
"packages/foo/x64-api-19/release/package_manifest.json",
],
"manifest_file": "packages/foo/x64-api-19/release/package_manifest.json"
},
...
]
}
```
Removing this makes the support of `sdk_use_deterministic_paths` [1] slightly
easier in the future.
[1] https://fuchsia-review.googlesource.com/c/fuchsia/+/1055900
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1056432
Original-Revision: dbc02cb705e9d1772bed6d60349cb7afd0b8ec87
GitOrigin-RevId: d9013aefd22ff38816aef04299ecde3e17de7e27
Change-Id: I737e1e549a34e0c66905b3949b7494c71d1a5de5
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.