Add an ebuild for the new factorytest-init package

chromeos-base/factorytest-init/factorytest-init-9999.ebuild

Index: chromeos-base/factorytest-init/factorytest-init-9999.ebuild
diff --git a/chromeos-base/factorytest-init/factorytest-init-9999.ebuild b/chromeos-base/factorytest-init/factorytest-init-9999.ebuild
new file mode 100644
index 0000000000000000000000000000000000000000..fdab388471deb821886210025bf34d42a15bbba8
--- /dev/null
+++ b/chromeos-base/factorytest-init/factorytest-init-9999.ebuild
@@ -0,0 +1,33 @@
+# Copyright (c) 2011 The Chromium OS Authors. All rights reserved.
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=2
+
+inherit cros-workon
+
+DESCRIPTION="Upstart jobs for the Chrome OS factory test image"
+HOMEPAGE="http://src.chromium.org"
+SRC_URI=""
+LICENSE="BSD"
+SLOT="0"
+KEYWORDS="~x86 ~arm"
+IUSE=""
+
+DEPEND=""
+
+RDEPEND="\
+	chromeos-base/chromeos-init
+	sys-apps/coreutils
+	sys-apps/module-init-tools
+	sys-apps/upstart
+	sys-process/procps
+	"
+
+CROS_WORKON_LOCALNAME="factory_test"
+CROS_WORKON_PROJECT="factory_test"

[davidjames, 2011/03/17 23:55:33]

Can you add factory_test to the full manifest first? cros_workon needs this in
order to rev your ebuild and know what git hash to point at. Otherwise,
preflight will fail with an error explaining that it can't find the commit id.

+
+src_install() {
+	insinto /etc/init
+	doins factory.conf
+	doins factorylog.conf
+}