| commit | be7b931efa401f2692b654278392c3169b813bcf | [log] [tgz] |
|---|---|---|
| author | Benjamin Lerman <qsr@chromium.org> | Tue Sep 25 13:59:41 2018 +0200 |
| committer | Benjamin Lerman <qsr@chromium.org> | Tue Sep 25 14:00:02 2018 +0200 |
| tree | 2c7eee47a3953005b55e40a16d3b56227304e3db | |
| parent | 3167a256bbbcc4f5ea0cbdc2e82b24ba5cac2a6a [diff] |
[fx] Do not unconditionally exit from fx-cmd-locked Only exit from fx-cmd-locked if the command failed. Change-Id: I20131749e591b3651b05774a7d41d67ac9eef93f
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.