commit | a7daf11c1abe33e0169d0a9dbd3acad908c3b52b | [log] [tgz] |
---|---|---|
author | James Robinson <jamesr@google.com> | Wed Jan 16 13:48:19 2019 -0800 |
committer | James Robinson <jamesr@google.com> | Wed Jan 16 18:49:04 2019 -0800 |
tree | d9d7107609a21328ebd1545d654ba258823ba959 | |
parent | f5d0db92d8dce3c8f425f93f606d950d69915152 [diff] |
[blobstats] Update blob stats script to use paths within packages This updates the blobstats script to display the paths to blobs based on the path name used by the package containing them. The underlying storage charges and proportional counts are still computed on a blob-by-blob bases, based off of their hash. This uses the blobs.json metadata file generated by the build to determine the paths within packages. Also restructures the internals of blobstats to reflect that blobs don't have a meaningful path outside the context of a particular package, and avoids recomputing hashes of blobs to speed up the calculations and simplify the code. Also marks unique blobs as unique. Test: run 'fx blobstats' on builds including prebuilt_package entries BLD-342 #done Change-Id: I0a6a8d40ae8ad77d362068b5fc58fcd7390b83d2
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.