On Thu, 2005-07-14 at 01:13 -0400, Kristian Benoit wrote:
> On Wed, 2005-07-13 at 20:02 -0400, Ned Ludd wrote:
> > On Wed, 2005-07-13 at 18:44 -0400, Kristian Benoit wrote:
> > > I'm trying to add a new command to ebuild (preconfig) for packages like
> But anyway, the question is not whether the idea is good or not, but how
> to get a menuconfig that works within ebuild.sh (called from spawn in
> portage_exec ... called from the user with ebuild or emerge)?
Well portage is a non-interactive tool and it's staying that way.
For what you want you will need to edit the busybox/-sources/uClibc
ebuild and manually add in a call to make menuconfig.
Or add something like this untested example to your
local /etc/portage/bashrc
if [[ $EBUILD_PHASE == compile ]]; then
case "$PN" in
busybox)
uclibc)
*-sources)
echo "we are at the stage where portage has unpacked the "
echo "ebuild and is getting ready to compile."
echo "being that no portage dev in his/her right mind would ever"
echo "allow interactive code in an ebuild we use bashrc tricks"
echo "here to get what Kristian is after"
/usr/bin/make menuconfig || exit 1
;;
esac
fi
--
Ned Ludd <[EMAIL PROTECTED]>
--
[email protected] mailing list
