From: Kristian Benoit <kbenoit@opersys.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-embedded] Interactive command
Date: Thu, 14 Jul 2005 10:37:48 -0400 [thread overview]
Message-ID: <1121351868.5971.52.camel@localhost> (raw)
In-Reply-To: <1121323391.7265.16.camel@localhost>
On Thu, 2005-07-14 at 08:43 +0200, Patrick Lauer wrote:
> On Thu, 2005-07-14 at 01:13 -0400, Kristian Benoit wrote:
> > What I want is "emerge busybox uclibc vanilla-sources nano". Should
> > unpack only the 3 first packages, show me busybox menuconfig, uclibc
> > menuconfig and vanilla-sources menuconfig and only then perform the rest
> > of the installation as usual (without re-unpacking the 3 packages).
> I really really hope that you want this to be a totally optional feature
> that is never ever enabled by default.
Of course it has to be totally optional and preconfig should be called
before any packages compilation. So that you get every preconfig
interactive prompt before everything else is done.
> When I run emerge -uD world on a server I don't accept any ebuild
> waiting for interactive input. For stagebuilding and other activities
> this behaviour is also unacceptable.
I wont accept that either :).
> > And
> > save the configs for futur use. So if my configs does not fit my need,
> > re-emerging busybox with USE=savedconfig should get me the busybox
> > menuconfig back using the previously configured ".config".
> Patch the ebuilds with your .config
Nope, it would just use the actual solution, use the one
in /etc/busybox/busybox.config
> > 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)?
> *shudder* I hope this stays limited to your overlay.
>
> wkr,
> Patrick
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-14 14:41 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 [this message]
2005-07-14 11:58 ` Ned Ludd
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=1121351868.5971.52.camel@localhost \
--to=kbenoit@opersys.com \
--cc=gentoo-dev@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