update hooks: make sure cross-compilers are not in @world

There was a bug in the setup_board where it was selecting cross-compilers
and adding them to @world.  Now that's been fixed, undo the damage.

BUG=None
TEST=`./update_chroot && grep ^cross- /var/lib/portage/world` showed nothing

Change-Id: Ide4961def700cf42d95454cc0ce404cb517bdfea
Reviewed-on: https://gerrit.chromium.org/gerrit/16997
Reviewed-by: Brian Harring <ferringb@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
This commit is contained in:
Mike Frysinger 2012-02-28 16:06:30 -05:00 committed by Gerrit
parent 21a27b75e9
commit 47d28794fa

View File

@ -0,0 +1,14 @@
# Copyright (c) 2012 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.
# There was a bug in the setup_board script where it added the cross-compilers
# to the @world set. Make sure we don't do that since letting emerge do the
# upgrade rather than crossdev (currently) doesn't work.
world="/var/lib/portage/world"
if [[ -e ${world} ]] ; then
sudo sed -i '/^cross-/d' "${world}"
fi
exit 0