| commit | 29e2002316655a46365832ef55c55e8fb23aee3c | [log] [tgz] |
|---|---|---|
| author | James Robinson <jamesr@google.com> | Wed Jan 23 13:53:56 2019 -0800 |
| committer | James Robinson <jamesr@google.com> | Mon Jan 28 17:27:48 2019 -0800 |
| tree | 732261e29f1035a6c77c4d7aeb271e8ddf026a17 | |
| parent | 7d4da804280bed7ca09ea5c1919ff80d03d5988b [diff] |
[blobstats] Fork blobstats visualization template, improve This forks the visualization template and dependencies of the blobstats tool and updates them to take into account features of blobs and packages, instead of pretending everything is a symbol in a binary. Improvements: * Update all terminology (symbol->blob, directory->package) * Add information about compressed and uncompressed sizes and reference count on shared blobs * Update colors to be more neutral * Update labels on entries to be more accurate * Update report naming and contents * Remove dead links * Add original and estimated compressed sizes to data model Also moves the code to its own directory and imports the d3 library instead of reaching into the Dart VM's internal directory. Test: fx blobstats Change-Id: I95cea2fa7e4c005d0917c991a726098326b00116
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.