A MetaContents represents the “meta/contents” file of a Fuchsia archive
file of a Fuchsia package.
It validates that all resource paths are valid and that none of them start
with “meta/”.
A MetaPackage represents the “meta/package” file of a meta.far (which is
a Fuchsia archive file of a Fuchsia package).
It validates that the name and variant (called “version” in json) are valid.
A MetaSubpackages represents the “meta/fuchsia.pkg/subpackages” file of a Fuchsia
archive file of a Fuchsia package. It validates that all subpackage names
are valid.
A PackageBuildManifest lists the files that should be included in a Fuchsia package. Both
external_contents and far_contents are maps from package resource paths in the to-be-created
package to paths on the local filesystem. Package resource paths start with “meta/” if and only
if they are in far_contents.
A builder for Fuchsia Packages
PackageManifestList is a construct that points at a path that contains a
package manifest list. This will be used by the packaging tooling to
understand when packages have changed.
A Fuchsia Package Name. Package names are the first segment of the path.
https://fuchsia.dev/fuchsia-src/concepts/packages/package_url#package-name
A Fuchsia Package Path. Paths must currently be “{name}/{variant}”.
A Fuchsia Package Variant. Package variants are the optional second segment of the path.
Helper type for reading the build-time information based on the subpackage
declarations declared in a build file (such as the subpackages list in
a fuchsia_package() target, in BUILD.gn).