Add an ebuild for the new factorytest-init package

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

+# 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="\

[Vince Laviano, 2011/03/18 02:15:05]

Stylistic nit. The convention that I've seen is for the first dependency to be
on the same line as the open quote and for the close quote to be on the same
line as the last dependency. An example is the "Ebuild with Dependencies"
section of http://devmanual.gentoo.org/quickstart/index.html.

[jrbarnette, 2011/03/18 18:56:12]

True.  I don't know what came over me here...

+        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"
+
+src_install() {
+        insinto /etc/init

[Vince Laviano, 2011/03/18 02:15:05]

This may be overly paranoid, but we might want to precede this line with "dodir
/etc/init" to ensure that this directory exists before installing into it.

[jrbarnette, 2011/03/18 18:56:12]

Ah.  Reading the relevant Gentoo docs, I see that we're not guaranteed
that the chromeos-init package will be merged before this package.
Which, sure enough, means we can't be guaranteed of the existence
of /etc/init...

+        doins factory.conf
+        doins factorylog.conf
+}