| 1 |
Hi |
| 2 |
|
| 3 |
On Sunday 19 May 2002 09:37, Scott J Garner wrote: |
| 4 |
> What is the prefered way to handle an ebuild for |
| 5 |
> software that requires some kind of user input to |
| 6 |
> configure and compile? |
| 7 |
Figuring out how to get around questions and supply default or tuned answers |
| 8 |
:). |
| 9 |
|
| 10 |
> The package I am dealing with specifically is |
| 11 |
> lirc. The recommended method for configuring it |
| 12 |
> is to run a dialog based config util which |
| 13 |
> generates the proper ./configure options. This |
| 14 |
> could be skipped, but some of the options are very |
| 15 |
> hardware specific. |
| 16 |
Like what kind of hardware? |
| 17 |
Architecture: use ARCH setting. |
| 18 |
Sound: there are alsa/oss use vars, |
| 19 |
etc. |
| 20 |
General idea: use whatever is listed in use.desc to figure out what options to |
| 21 |
pass to confgure. If you feel a need to introduce new use flag, you can make |
| 22 |
that proposal. If you will be able to show that this usevar will be usefull |
| 23 |
as well somewere else chances are good that usevar will be accepted. |
| 24 |
Grep through ebuilds for "use " to see the examples. RTFM helps as well |
| 25 |
(ebuild developer howto) :). |
| 26 |
|
| 27 |
George |
Archives