Here's how you add a new package to Chromium OS:
- Create an ebuild file for your package
src/third_party/chromiumos-overlay/. See the ebuild(5) man page (from within your development chroot) and the other ebuilds in
Upload the package to Localmirror of Google (require Google account).
- for example, the ebuild file of systemtap is placed in
Create a README.chromiumos file that describes the purpose of the package. If your package is a third-party package, document any custom patches that have been applied
Add a dependency to your new package in one of:
Increment the revision number of the ebuild that you modified so that incremental builds recognize the changes.
- Includes the package in all images (base/release, developer, test)
- Includes the package in developer and test images
- Includes the package in test images
- Includes the package in the SDK itself
The source code of the package shouldn't be placed in the
src/. emerge will download the package and store it in
/var/lib/portage/distfiles-target/, and the code is compiled in
/build/tegra2_seaboard/tmp/portage/. When porting a new package, we can put the package in
Once you're done, make sure your changes to do not break the build system. Then create a changelist and get it reviewed (see Contributing Code for details).
Adding a package to a running Chromium OS system
The easiest way to add a new package, or update a package is to start
devserver on the build host, and use
gmerge to build the package and install the results on the target device.
See Using the dev server.
Adding a package to the manifest
See the Git server-side information site for information about how to add your package to a manifest.