Re: [gentoo-dev] ebuild requiring user input

[JR Boyens]

You probably going to have to patch the Makefile...

or

I believe that the ALSA ebuild has an optional shell var that says
what cards will be built, which would be similar to what you want. :)

On Mon, May 20, 2002 at 01:25:04AM -0500 or thereabouts, Scott J Garner wrote:
> Ok, I must not have explained this very well...
>
> It wasn't my intention to have the ebuild require
> user intervention by default, but as an option if
> need be (as indicated at the end of the message).
>
> The hardware in question is the ir controller for
> the remote to use which can be any number of
> external or onboard devices.  There is a configure
> option for "any" driver which would allow for a
> automatic ebuild and would be default.  The
> problem with that is that it doesn't build all of
> the drivers--specifically leaving out those that
> require a lirc kernel module.
>
> This problem seems beyond the scope of use vars to
> me...in my eyes the solution is to use the "any"
> driver by default and if this didn't sufficient
> allow the user to specify the proper options.  The
> question then is, do I just allow for them to
> enter the required configure options by hand or
> provide someway to use the dialog based config
> util or both?
>
> I suppose it would be possible to store the ir
> related data someplace in etc, but it varies so
> much from system to system and would be used so
> rarely it seems overkill.
>
> It would be really nice if this problem was
> avoidable, but for some reason the authors of lirc
> decided one should tweak all of the settings
> before compile instead of after as usual.
>
>
>
> On Sun 19 May 2002 at 14:16 -0500,
> George Shapovalov wrote:
>
> > Hi
> >
> > On Sunday 19 May 2002 09:37, Scott J Garner wrote:
> > > What is the prefered way to handle an ebuild for
> > > software that requires some kind of user input to
> > > configure and compile?
> > Figuring out how to get around questions and supply default or tuned answers
> > :).
> >
> > > The package I am dealing with specifically is
> > > lirc.  The recommended method for configuring it
> > > is to run a dialog based config util which
> > > generates the proper ./configure options.  This
> > > could be skipped, but some of the options are very
> > > hardware specific.
> > Like what kind of hardware?
> > Architecture: use ARCH setting.
> > Sound: there are alsa/oss use vars,
> > etc.
> > General idea: use whatever is listed in use.desc to figure out what options to
> > pass to confgure. If you feel a need to introduce new use flag, you can make
> > that proposal. If you will be able to show that this usevar will be usefull
> > as well somewere else chances are good that usevar will be accepted.
> > Grep through ebuilds for "use " to see the examples. RTFM helps as well
> > (ebuild developer howto) :).
> >
> > George
> >
> > _______________________________________________
> > gentoo-dev mailing list
> > gentoo-dev@g.o
> > http://lists.gentoo.org/mailman/listinfo/gentoo-dev
> >
>
> --
> -                 Scott J Garner                 -
> -                Austin, TX - USA                -
> -           AIM: Jungalero  OPN: MrFab           -
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@g.o
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
>