From: Ned Ludd <solar@gentoo.org>
To: gentoo-embedded@lists.gentoo.org
Cc: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: [gentoo-embedded] Interactive command
Date: Thu, 14 Jul 2005 07:58:00 -0400 [thread overview]
Message-ID: <1121342280.10953.20.camel@localhost> (raw)
In-Reply-To: <1121317999.5993.27.camel@localhost>
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 <solar@gentoo.org>
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-14 12:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-13 22:44 [gentoo-dev] Interactive command Kristian Benoit
2005-07-13 23:49 ` Donnie Berkholz
2005-07-14 14:45 ` Kristian Benoit
2005-07-14 0:02 ` [gentoo-dev] Re: [gentoo-embedded] " Ned Ludd
2005-07-14 5:13 ` Kristian Benoit
2005-07-14 6:43 ` Patrick Lauer
2005-07-14 14:37 ` Kristian Benoit
2005-07-14 11:58 ` Ned Ludd [this message]
2005-07-14 12:37 ` Jason Stubbs
2005-07-14 14:56 ` Kristian Benoit
2005-07-16 9:20 ` Drake Wyrm
2005-08-23 13:41 ` Paul de Vrieze
2005-08-23 15:12 ` Jason Stubbs
2005-08-25 11:23 ` Paul de Vrieze
2005-07-14 14:29 ` Kristian Benoit
2005-07-14 16:01 ` Michael Cummings
2005-07-14 16:51 ` Kristian Benoit
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1121342280.10953.20.camel@localhost \
--to=solar@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=gentoo-embedded@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox