commit | 99b70d610c78b7022441000ded319e7450f8f9d6 | [log] [tgz] |
---|---|---|
author | Vardhan Mudunuru <vardhan@google.com> | Wed Mar 21 12:39:58 2018 -0700 |
committer | Vardhan Mudunuru <vardhan@google.com> | Wed Mar 21 20:38:27 2018 +0000 |
tree | cfe64c69222dfab12ffeee888a4b1ef51d178d6d | |
parent | eb3ba27685a990e4e0e2844fa38d1d2312a5f2e0 [diff] |
[push-package] Trigger on-device module_resolver to index a pushed package. `fx push-package` should now try to trigger the module_runner to index the module manifest inside the package if it exists. Note that this only works if a user is logged in (since module_runner runs under a user). Putting this trigger logic inside push-package is not the final goal and will go away altogether once we have more infrastructure in place, but for now will eleviate a lot of development burden that the upper layers face when doing module development. MI4-897 Change-Id: I16f63cc2c115572ac1f776e2dfdb8976f31e3f5c
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.