| 1 |
Ok, I must not have explained this very well... |
| 2 |
|
| 3 |
It wasn't my intention to have the ebuild require |
| 4 |
user intervention by default, but as an option if |
| 5 |
need be (as indicated at the end of the message). |
| 6 |
|
| 7 |
The hardware in question is the ir controller for |
| 8 |
the remote to use which can be any number of |
| 9 |
external or onboard devices. There is a configure |
| 10 |
option for "any" driver which would allow for a |
| 11 |
automatic ebuild and would be default. The |
| 12 |
problem with that is that it doesn't build all of |
| 13 |
the drivers--specifically leaving out those that |
| 14 |
require a lirc kernel module. |
| 15 |
|
| 16 |
This problem seems beyond the scope of use vars to |
| 17 |
me...in my eyes the solution is to use the "any" |
| 18 |
driver by default and if this didn't sufficient |
| 19 |
allow the user to specify the proper options. The |
| 20 |
question then is, do I just allow for them to |
| 21 |
enter the required configure options by hand or |
| 22 |
provide someway to use the dialog based config |
| 23 |
util or both? |
| 24 |
|
| 25 |
I suppose it would be possible to store the ir |
| 26 |
related data someplace in etc, but it varies so |
| 27 |
much from system to system and would be used so |
| 28 |
rarely it seems overkill. |
| 29 |
|
| 30 |
It would be really nice if this problem was |
| 31 |
avoidable, but for some reason the authors of lirc |
| 32 |
decided one should tweak all of the settings |
| 33 |
before compile instead of after as usual. |
| 34 |
|
| 35 |
|
| 36 |
|
| 37 |
On Sun 19 May 2002 at 14:16 -0500, |
| 38 |
George Shapovalov wrote: |
| 39 |
|
| 40 |
> Hi |
| 41 |
> |
| 42 |
> On Sunday 19 May 2002 09:37, Scott J Garner wrote: |
| 43 |
> > What is the prefered way to handle an ebuild for |
| 44 |
> > software that requires some kind of user input to |
| 45 |
> > configure and compile? |
| 46 |
> Figuring out how to get around questions and supply default or tuned answers |
| 47 |
> :). |
| 48 |
> |
| 49 |
> > The package I am dealing with specifically is |
| 50 |
> > lirc. The recommended method for configuring it |
| 51 |
> > is to run a dialog based config util which |
| 52 |
> > generates the proper ./configure options. This |
| 53 |
> > could be skipped, but some of the options are very |
| 54 |
> > hardware specific. |
| 55 |
> Like what kind of hardware? |
| 56 |
> Architecture: use ARCH setting. |
| 57 |
> Sound: there are alsa/oss use vars, |
| 58 |
> etc. |
| 59 |
> General idea: use whatever is listed in use.desc to figure out what options to |
| 60 |
> pass to confgure. If you feel a need to introduce new use flag, you can make |
| 61 |
> that proposal. If you will be able to show that this usevar will be usefull |
| 62 |
> as well somewere else chances are good that usevar will be accepted. |
| 63 |
> Grep through ebuilds for "use " to see the examples. RTFM helps as well |
| 64 |
> (ebuild developer howto) :). |
| 65 |
> |
| 66 |
> George |
| 67 |
> |
| 68 |
> _______________________________________________ |
| 69 |
> gentoo-dev mailing list |
| 70 |
> gentoo-dev@g.o |
| 71 |
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev |
| 72 |
> |
| 73 |
|
| 74 |
-- |
| 75 |
- Scott J Garner - |
| 76 |
- Austin, TX - USA - |
| 77 |
- AIM: Jungalero OPN: MrFab - |
Archives