You feed it the output of cros_extract_deps and you get pretty pictures:
./cros_extract_deps --board x86-generic chromeos chromeos-dev |./cros_generate_deps_graphs -o output -c -l
Review URL: http://codereview.chromium.org/2840020
Other changes:
- Added update_base_packages() method.
- Fix a get_latest_image.sh problem when the image does not already exist.
- Cleanup method invocations, and remove OUTPUT_IMG global variable.
- Add kernel testing logic back (it was accidentally deleted in an earlier patch.)
TEST=Built regular image. Updated old image to contain new packages.
BUG=none
Patch by: Don Garrett <dgarrett@chromium.org>
(Tweaked by me to address review feedback.)
Review URL: http://codereview.chromium.org/2857020
We want build_image to honour the configuration in PORTDIR and only use
the latest stable version as known by portage and the overlays.
We get these semantics with --usepkg. We do not get them with --usepkgonly.
The one downside is that instead of failing when you forget to run
build_packages before build_image, build_image will try to build
packages from source.
From "man emerge":
--usepkg[=n] (-k)
Tells emerge to use binary packages (from $PKGDIR) if they
are available, thus possibly avoiding some time-consuming
compiles. This option is useful for CD installs; you can
export PKGDIR=/mnt/cdrom/packages and then use this option
to have emerge "pull" binary packages from the CD in order
to satisfy dependencies.
--usepkgonly[=n] (-K)
Tells emerge to only use binary packages (from $PKGDIR).
All the binary packages must be available at the time of
dependency calculation or emerge will simply abort.
Portage does not use $PORTDIR when calculating dependency
information so all masking information is ignored.
Change-Id: I267dad8992ac683d0ff4db0d0c72baba61ecbccf
Review URL: http://codereview.chromium.org/2874013
Makes kernel partition creation standalone. This is motivated
both by the ability to build test kernel partitions easily as well
the need to create all kernel command line configuration after the
rootfs has been completely created.
Instead of a massive overhaul, I'll do this refactor in pieces.
TEST=manually rebuilt the image
BUG=chromium-os:327
Review URL: http://codereview.chromium.org/2825021
to handle changed command line arguments, and attempt
to make it resilient in the face of future changes.
TEST=Run script on fresh image; confirm that '-I eth_test' is present on the exec line of /etc/init/flimflam.conf
Review URL: http://codereview.chromium.org/2842023
Moves ebuild(s) between stable and live states.
Lists ebuilds currently under development in the testing branch.
Stable ebuilds obtain and build against the last known good commit.
Live ebuilds (9999) perform a 'git clone' during the src_unpack
step to obtain and save the source for development and building.
Example usage:
Sync & build 'ibus-hangul' testing ebuild (9999)
./cros_workon start app-i18n/ibus-hangul
Build 'ibus-hangul' from the last stable commit
./cros_workon stop app-i18n/ibus-hangul
List of ebuilds under development
./cros_workon list
Change-Id: I2ea4babd7597d5cea9ca96419a74152f9f0b23f1
Note: --board must be specified if the --default option
to setup_board was not used.
Review URL: http://codereview.chromium.org/2852019
This is to solve the problem where a build-bot is kicked off for a
tree that has no changes in it. This should not happen often.
Review URL: http://codereview.chromium.org/2873010
update_dev_packages, and update_recovery_packages created.
Moved assorted global variables up to the top section, since they are global.
TEST=Ran build_image.
BUG=none
Review URL: http://codereview.chromium.org/2823010
This does nothing, except provide a way to determine which of the three
possible boot methods was used to boot the running image. Handy for
debugging BIOS issues on experimental and dogfood machines.
Review URL: http://codereview.chromium.org/2868010
TEST=Ran unittests with 2 test failures (powerd and update engine).
Will check with authors to fix these before moving the default over
to this.
Review URL: http://codereview.chromium.org/2837004
This script is internal only.
BUG=none
TEST=Built and installed image.
Review URL: http://codereview.chromium.org/2819003
Change-Id: I4426a0e939862211a0527de07aefbea74ab0e092
Fix the bug happened to me that the script completed but the data haven't completely been written to disk.
Review URL: http://codereview.chromium.org/2831001
Since different platforms have different instructions to update their firmware.
In order not to depend on the install shim, we pack all firmware update files
into a single file, i.e. an executable shell script with embedded files.
The original CL (http://codereview.chromium.org/2366001) is reviewed and is
broken down into 5 CLs. This is one of them.
Review URL: http://codereview.chromium.org/2792013
* This also adds reverse sort into the umount list, because of cascading mounts, so that /foo/anything is always before /foo, and as such is always unmounted first. If the list were not sorted, "mount point busy" errors might occur, depending on various conditions.
TEST=
1) With a previously created chroot, I ran enter_chroot.sh, and got the correct prompt. After logging out of that prompt, everything else was correctly unmounted, without any error messages. When entering chroot twice from two different shells, everything was correctly unmounted after the last shell exited.
2) Repeat 1 but with cleanly created chroot just for this purpose.
3) In the chroot, make packages for one board (x86-generic) using build_packages
4) The messages "openpty failed: 'out of pty devices'" whenever trying to emerge anything (or other commands looking up pts) have disappeared.
Review URL: http://codereview.chromium.org/2714010
