Packaging:
- Adds packaging for minijail
- Adds support for building minijail in the chroot (libcap-dev)
- Fixes libcap2 versioning to be compatible with libcap-dev in the repo
- Build minijail as part of the platform packages
Code:
- Fixed an initialization check bug in minijail and unittests
Review URL: http://codereview.chromium.org/465106
- scripts/build_platform_packages.sh
Run third_party/{ibus, ibus-chewing, ibus-anthy}/make_pkg.sh scripts in order to create IBus debian packages.
- third_party/ibus/make_pkg.sh
- third_party/ibus-chewing/make_pkg.sh
- third_party/ibus-anthy/make_pkg.sh
New files.
- third_party/ibus-chewing/ibus-chewing_1.2.0.20090818-2.diff.gz
- third_party/ibus-anthy/ibus-anthy_1.2.0.20090813-2.diff.gz
New files. These patch files create debian/ directories under third_party/ibus-chewing/ and third_party/ibus-anthy/ respectively.
These files are copied from Ubuntu Karmic's deb source packages, just like third_party/clutter/clutter-1.0_1.0.4-0ubuntu1.diff.gz (I believe it's okay, but let me double-check).
- package_repo/package-list-prod.txt
- package_repo/repo_list_image.txt
Add IBus packages to the rootfs image.
- package_repo/package-list-dev.txt
Add debian packages that are necessary to build IBus packages. Please note that autopoint script in gettext package requires cvs for unknown reasons.
- package_repo/repo_list_dev.txt
* IBus code requires slightly newer version of Gtk+/Glib. Upgraded them from 2.17.2-0ubuntu2 to 2.17.7-0ubuntu3 (Gtk+), from 2.21.2-0ubuntu1 to 2.21.4-0ubuntu1 (Glib).
* cmake-data depends on emacsen-common and update-indetd.
* python-gobject-dev depends on libffi-dev.
* python2.6-dev is required, but python2.6-dev_2.6.2-0ubuntu2 is not available on Ubuntu (I don't know why). Therefore, upgraded all python2.6* packages from 2.6.2-0ubuntu2 to 2.6.2-0ubuntu3.
Review URL: http://codereview.chromium.org/434033
Review URL: http://codereview.chromium.org/444016
git-svn-id: svn://chrome-svn/chromeos/trunk@325 06c00378-0e64-4dae-be16-12b19f9950a1
* Remove deb patch support
* Fix --config to actually work
* Other cleanup
Review URL: http://codereview.chromium.org/436043
git-svn-id: svn://chrome-svn/chromeos/trunk@321 06c00378-0e64-4dae-be16-12b19f9950a1
Still seeing some bugs get filed related to this. I went through
all of the scripts, but let me know if I missed any.
Review URL: http://codereview.chromium.org/432002
git-svn-id: svn://chrome-svn/chromeos/trunk@306 06c00378-0e64-4dae-be16-12b19f9950a1
This fixes monospace fonts in Chrome. This change also
moves some static files out of customize_rootfs.sh.
BUG=237
Review URL: http://codereview.chromium.org/424011
git-svn-id: svn://chrome-svn/chromeos/trunk@303 06c00378-0e64-4dae-be16-12b19f9950a1
The build_image script now calls install_packages.sh followed
by customize_rootfs.sh.
The current system installs packages and performs customization
fixups from within the rootfs it is building. In order to
cross-build properly we'll need to do these steps from outside
of the root. Splitting package installation and rootfs customization
will make it easier to do this. A follow-on change will modify
customize_rootfs to run from outside of the rootfs.
Review URL: http://codereview.chromium.org/414051
git-svn-id: svn://chrome-svn/chromeos/trunk@300 06c00378-0e64-4dae-be16-12b19f9950a1
- Rev chromeos-systemtests, and add fio as a dependency.
- Add fio into the image during mod_image_for_test.sh
Review URL: http://chromereview.prom.corp.google.com/1180028
git-svn-id: svn://chrome-svn/chromeos/trunk@297 06c00378-0e64-4dae-be16-12b19f9950a1
their own init script in /etc/init.
This changes the chromeos-init package to install our
init scripts in /etc/init.chromeos. In the customize_rootfs
stage we remove /etc/init and replace with our init scripts.
Review URL: http://chromereview.prom.corp.google.com/1187069
git-svn-id: svn://chrome-svn/chromeos/trunk@264 06c00378-0e64-4dae-be16-12b19f9950a1
should depend on the installer package.
Move postinst out of customize_rootfs and into the installer
package (at least for now).
Review URL: http://chromereview.prom.corp.google.com/1187059
git-svn-id: svn://chrome-svn/chromeos/trunk@252 06c00378-0e64-4dae-be16-12b19f9950a1
But, we still explictly require bootchart-java, to create the pretty picture.
Without explicitly adding bootchart-java, it removes these packages:
bootchart-java
ca-certificates-java
default-jre-headless
gcj-4.4-base
gcj-4.4-jre
gcj-4.4-jre-headless
gcj-4.4-jre-lib
gcj-jre
gcj-jre-headless
icedtea-6-jre-cacao
java-common
libcommons-cli-java
libcommons-compress-java
libcommons-lang-java
libgcj-common
libgcj10
libgcj10-awt
libjline-java
liblcms1
openjdk-6-jre-headless
openjdk-6-jre-lib
python-central
rhino
tzdata-java
By explicitly adding bootchart-java it removes only these packages:
gcj-4.4-jre-lib
icedtea-6-jre-cacao
Either way, bootchart still collects the data so it is possible to generate
the pictures remotely.
Review URL: http://chromereview.prom.corp.google.com/1188035
git-svn-id: svn://chrome-svn/chromeos/trunk@225 06c00378-0e64-4dae-be16-12b19f9950a1
This removes the acpi stuff from customize_rootfs and should make it easier
to do more acpi stuff in the future as needed. We still need to figure out
how to handle acpi across different devices.
Review URL: http://chromereview.prom.corp.google.com/1186038
git-svn-id: svn://chrome-svn/chromeos/trunk@220 06c00378-0e64-4dae-be16-12b19f9950a1
Fixes the following error:
rm: cannot remove `/home/chrome-bot/trunk/src/build/x86/local_packages/linux-image-*.deb': No such file or directory
Review URL: http://chromereview.prom.corp.google.com/1186034
git-svn-id: svn://chrome-svn/chromeos/trunk@215 06c00378-0e64-4dae-be16-12b19f9950a1
Already moved config into the kernel git repo. This change fixes the
build to use the config which is in the kernel and removes the configs
in the chromeos repo.
Also removed a lot of the kernel version hard-coding that is in the build.
Review URL: http://chromereview.prom.corp.google.com/1188031
git-svn-id: svn://chrome-svn/chromeos/trunk@214 06c00378-0e64-4dae-be16-12b19f9950a1
stuff that parses a bunch of files in favor of just starting
our session script under a console-kit session. We don't need
any of the typical Xsession start stuff and this is simpler to
understand. Since we don't use Xsession.d, we no longer need
to delete certain files from that directory.
The CL also has the login_manager package install our own slim.conf
so that we don't need to be modifying the default one using sed
from customize_rootfs and the login_manager maintainer scripts.
Review URL: http://chromereview.prom.corp.google.com/1188025
git-svn-id: svn://chrome-svn/chromeos/trunk@209 06c00378-0e64-4dae-be16-12b19f9950a1
A few changes here.
1. A simple webui for building packages in the source tree.
2. A shell script that you can run on your netbook to kick of a build of a given package, download the result, and install it.
3. Refactored update/build functionality into classes so that the build env paths can be shared.
4. devkit.sh downloads an upsatart task that starts ssh at boot time.
More info in the dev server manual -
https://docs.google.com/a/google.com/Doc?docid=0AT6qlIKi36JQY2M1Y3B2bWNfMTZkems5eGducg&hl=en
Review URL: http://chromereview.prom.corp.google.com/1187017
git-svn-id: svn://chrome-svn/chromeos/trunk@207 06c00378-0e64-4dae-be16-12b19f9950a1
We should no longer try to connect to googleguest or another open network at boot time. First time users will need to connect via ethernet to log into the machine. Once a user has logged in for the first time they will be able to login without network connectivty. Also, Connman will automatically connect to any available networks that the user has connected to in the past.
The long term solution for first time usage is to put the network picker in the login UI.
Review URL: http://chromereview.prom.corp.google.com/1187008
git-svn-id: svn://chrome-svn/chromeos/trunk@191 06c00378-0e64-4dae-be16-12b19f9950a1
