1 |
On Thu, 2005-07-14 at 07:58 -0400, Ned Ludd wrote: |
2 |
> On Thu, 2005-07-14 at 01:13 -0400, Kristian Benoit wrote: |
3 |
> > On Wed, 2005-07-13 at 20:02 -0400, Ned Ludd wrote: |
4 |
> > > On Wed, 2005-07-13 at 18:44 -0400, Kristian Benoit wrote: |
5 |
> > > > I'm trying to add a new command to ebuild (preconfig) for packages like |
6 |
> |
7 |
> |
8 |
> > But anyway, the question is not whether the idea is good or not, but how |
9 |
> > to get a menuconfig that works within ebuild.sh (called from spawn in |
10 |
> > portage_exec ... called from the user with ebuild or emerge)? |
11 |
> |
12 |
> Well portage is a non-interactive tool and it's staying that way. |
13 |
> For what you want you will need to edit the busybox/-sources/uClibc |
14 |
> ebuild and manually add in a call to make menuconfig. |
15 |
> Or add something like this untested example to your |
16 |
> local /etc/portage/bashrc |
17 |
|
18 |
I'm not trying to make it more interactive than it actually is. |
19 |
|
20 |
stated from: |
21 |
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=6#doc_chap3 |
22 |
|
23 |
"Performing Configuration Actions |
24 |
|
25 |
Some applications include instructions that configure the package |
26 |
further on your system. These instructions can be interactive and are |
27 |
therefore not automatically executed. To run these configuration steps, |
28 |
which are enlisted in the ebuild's (optional) config() function, use |
29 |
ebuild's config functionality: |
30 |
|
31 |
|
32 |
Code Listing 11: Configuring a package |
33 |
|
34 |
|
35 |
# ebuild path/to/ebuild config" |
36 |
|
37 |
I'm trying to do the same as config does, but in as a preconfig that |
38 |
would only be also called on user request. |
39 |
|
40 |
My goal is actually mostly learning portage internal so it might never |
41 |
do it's way into production and it might be fine like that. |
42 |
|
43 |
Thanks for the bashrc tip, I did'nt know that. |
44 |
|
45 |
Kristian |
46 |
|
47 |
-- |
48 |
gentoo-embedded@g.o mailing list |