On Thu, 2005-07-14 at 07:58 -0400, Ned Ludd wrote: > 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
I'm not trying to make it more interactive than it actually is. stated from: http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=6#doc_chap3 "Performing Configuration Actions Some applications include instructions that configure the package further on your system. These instructions can be interactive and are therefore not automatically executed. To run these configuration steps, which are enlisted in the ebuild's (optional) config() function, use ebuild's config functionality: Code Listing 11: Configuring a package # ebuild path/to/ebuild config" I'm trying to do the same as config does, but in as a preconfig that would only be also called on user request. My goal is actually mostly learning portage internal so it might never do it's way into production and it might be fine like that. Thanks for the bashrc tip, I did'nt know that. Kristian -- gentoo-dev@gentoo.org mailing list
