Add an ebuild for the new factorytest-init package

chromeos/scripts/build_packages

 #!/bin/bash
 
-# Copyright (c) 2010 The Chromium OS Authors. All rights reserved.
+# Copyright (c) 2011 The Chromium OS Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 # Script to build the set of binary packages needed by Chrome OS. It will
 # cross compile all of the packages into the given targets root and build
 # binary packages as a side-effect. The output packages will be picked up
 # by the build_image script to put together a bootable Chrome OS image.
 
 # Load common CrOS utilities.  Inside the chroot this file is installed in
 # /usr/lib/crosutils.  Outside the chroot we find it relative to the script's
@@ skipping 165 matching lines @@
 if [[ -n "${CHROME_ORIGIN}" ]]; then
   CROS_WORKON_PKGS="${CROS_WORKON_PKGS} chromeos-base/chromeos-chrome"
 fi
 
 PACKAGES="chromeos-base/chromeos"
 if [[ "${FLAGS_withdev}" -eq "${FLAGS_TRUE}" ]]; then
   PACKAGES="${PACKAGES} chromeos-base/chromeos-dev"
 fi
 if [[ "${FLAGS_withfactory}" -eq "${FLAGS_TRUE}" ]]; then
   PACKAGES="${PACKAGES} chromeos-base/chromeos-factoryinstall"
+  PACKAGES="${PACKAGES} chromeos-base/factorytest-init"

[davidjames, 2011/03/18 00:03:12]

Could you split this into a separate CL? We need to wait until factorytest-init
is 'marked as stable' by the buildbot before it's added as a dependency for the
build.

 fi
 if [[ "${FLAGS_withtest}" -eq "${FLAGS_TRUE}" ]]; then
   PACKAGES="${PACKAGES} chromeos-base/chromeos-test"
 fi
 if [[ "${FLAGS_withautotest}" -eq "${FLAGS_TRUE}" ]]; then
   PACKAGES="${PACKAGES} chromeos-base/autotest-all"
 fi
 # HACK ALERT
 # Remove chromeos-base/kernel: http://crosbug.com/11124
 # TODO(msb): remove this hack after 02/20/2011
@@ skipping 40 matching lines @@
 
     # Update the remainder of the packages.
     eretry ${EMERGE_BOARD_CMD} -uDNv ${EMERGE_FLAGS} ${PACKAGES}
   fi
 fi
 
 
 echo "Builds complete"
 print_time_elapsed
 echo "Done"