1 |
Pete Gavin wrote: |
2 |
|
3 |
> Hi, |
4 |
> |
5 |
> I was wondering... Is it required that an ebuild script be completely |
6 |
> non-interactive? |
7 |
|
8 |
Yes, otherwise there would be no autobuild. |
9 |
|
10 |
> I have a few ideas for the kernel configuration |
11 |
> scripts. I think it might be cool for the for the ebuild to ask the |
12 |
> installer if he/she wants to load a .config file from somewhere else, then |
13 |
> run make menuconfig. That way all the modules and stuff can be removed |
14 |
> with portage-unmerge. |
15 |
|
16 |
You can do this. |
17 |
After running "ebuild linux.... unpack" cd to |
18 |
/tmp/portage/linux.../work/linux |
19 |
run "make menuconfig/xconfig" |
20 |
Then continue with ebuild linux... compile |
21 |
|
22 |
Another possibility would be using the "config" function in ebuild. This was |
23 |
normaly intedet to be used |
24 |
for an opional additional configuration-layer. And should normaly modify the |
25 |
package configuration |
26 |
files from templates/databses whatever. Normaly this functions hsould be |
27 |
called after pkg_merge. |
28 |
But since we have no configuration layer right now and config is only used by |
29 |
a few packages (for example |
30 |
qmail runs config-fast from within the config function) we could use the |
31 |
config function for such an |
32 |
interactive thing. |
33 |
Another solution could be using a USE variable to decide if the manual |
34 |
configuration you described should be |
35 |
run or a variable that just triggers if a private config file should be used |
36 |
instead of the default one. Or we could make a sepearate kernel package that |
37 |
does these manual steps. |
38 |
|
39 |
But what do you think about that. The kernel ebuild looks if a file (for |
40 |
example /etc/kernel/[version].config) exists. If so it uses this instead of |
41 |
the default one. |
42 |
If you want to configure the kernel for the first time you can do it as I |
43 |
described above. The copy the .config file to /etc/kernel/[version].config |
44 |
and the next time you compile the kernel your private config file gets used. |
45 |
|
46 |
achim~ |
47 |
|
48 |
> |
49 |
> Pete |
50 |
> |
51 |
> _______________________________________________ |
52 |
> gentoo-dev mailing list |
53 |
> gentoo-dev@g.o |
54 |
> http://www.gentoo.org/mailman/listinfo/gentoo-dev |