commit | 9f6285c0e9e10e70729ac62c28fb12b53c02f805 | [log] [tgz] |
---|---|---|
author | Kevin Wells <kevinwells@google.com> | Tue Jan 15 15:58:09 2019 -0800 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Fri Jan 18 01:28:14 2019 +0000 |
tree | 2929268d1b621d87d2a0c3814fd394f3a8c6ff56 | |
parent | a7daf11c1abe33e0169d0a9dbd3acad908c3b52b [diff] |
[fx][delta] Invoke pm directly Invoke pm directly instead of proxying through fx, similar to how serve-updates invokes it. When building product configs that don't include pm, "fx pm" fails to find the binary. Test: manual Change-Id: Id585f52de81ca9c1cdd94ec127e5a0f5126c7763
This repository is for scripts useful when hacking on Fuchsia. This repository should contain scripts that perform tasks spanning multiple repositories. Scripts that only operate within a single repository should live in the relevant repository.
The push-package.py script pushes the files listed in the given manifests files. No checking is performed for incremental changes.
The sample command lines below can be used to build Modular and then push those files to the default device. This assumes you have already booted your device with a version of Fuchsia that contains the most recent version of all other packages. This command line uses the “system_manifest” file from each of the modular directories, such as modular, modular_dev, and modular_tests.
cd $FUCHSIA_DIR fx build peridot:modular_all scripts/push-package.py out/debug-x64/package/modular*/system_manifest
fx publish
will take a package from the build and create a Fuchsia package manager package from a build package. It will then add the package to a local update respository which, by default, is put at ${FUCHSIA_BUILD_DIR}/amber-files
. It will also add the package content files to the update repository and name these file after their Merkle Root. If a package name is supplied to fx publish
, only that package will be processed. If no name is supplied, all the packages made by the build will be included.