From fa4d2ebcf920dbfb3a0cabaa6d28f3b46a948fc3 Mon Sep 17 00:00:00 2001 From: Chris Gianelloni Date: Fri, 25 Apr 2008 15:16:48 +0000 Subject: [PATCH] Added emerge --info to debug output. I don't know why I didn't add it before. git-svn-id: svn+ssh://svn.gentoo.org/var/svnroot/catalyst/trunk@1403 d1e1f19c-881f-0410-ab34-b69fee027534 --- ChangeLog | 4 ++++ targets/support/chroot-functions.sh | 3 +++ 2 files changed, 7 insertions(+) diff --git a/ChangeLog b/ChangeLog index b9602784..e02effe9 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,6 +1,10 @@ # Copyright 2002-2008 Gentoo Foundation; Distributed under the GPL v2 # $Id: $ + 25 Apr 2008; Chris Gianelloni + targets/support/chroot-functions.sh: + Added emerge --info to debug output. I don't know why I didn't add it before. + 25 Apr 2008; Chris Gianelloni targets/stage1/stage1-preclean-chroot.sh, targets/stage2/stage2-preclean-chroot.sh, diff --git a/targets/support/chroot-functions.sh b/targets/support/chroot-functions.sh index f90a4d93..b88b2d20 100755 --- a/targets/support/chroot-functions.sh +++ b/targets/support/chroot-functions.sh @@ -265,6 +265,9 @@ show_debug() { echo "Profile/target info:" echo "Profile inheritance:" python -c 'import portage; print portage.settings.profiles' + echo + # TODO: make this work on non-portage + emerge --info # TODO: grab our entire env # to get see the ebuild env you can do something like: # `set > /tmp/env_dump.${EBUILD_PHASE}` inside /etc/portage/bashrc -- 2.26.2