[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <s5h8wyvwnld.wl%tiwai@suse.de>
Date: Wed, 30 Apr 2008 14:09:50 +0200
From: Takashi Iwai <tiwai@...e.de>
To: Sam Ravnborg <sam@...nborg.org>
Cc: David Miller <davem@...emloft.net>, mingo@...e.hu,
mchehab@...radead.org, akpm@...ux-foundation.org,
linux-dvb-maintainer@...uxtv.org, video4linux-list@...hat.com,
linux-kernel@...r.kernel.org, efault@....de
Subject: Re: [patch, -git] media/video/sound build fix, TEA5761/TEA5767
At Wed, 30 Apr 2008 13:29:59 +0200,
Sam Ravnborg wrote:
>
> On Wed, Apr 30, 2008 at 04:17:03AM -0700, David Miller wrote:
> > From: Takashi Iwai <tiwai@...e.de>
> > Date: Wed, 30 Apr 2008 13:11:31 +0200
> >
> > > IMO, it's the reverse selection from sound to V4L that makes things
> > > complicated. I believe it's better to fix it as a normal dependency.
> > >
> > > How about the patch below?
> >
> > The question that remains is what does this mean for users?
> >
> > How does a user, who wants to enable this 'sound' driver,
> > learn that they must enable the v4l subsystem in order to
> > do so?
>
> [OT to the actual problem]
>
> I have envisioned something like a "requires tag" that
> would list what a config symbols needs.
>
> Like in this case it would have been:
>
> requires V4L
>
> This should in the frontends then if the user selects a symbol
> where the 'requires' are not satisfied with a window listing
> the menuentries for the symbol that the user needs to
> enable to satisfy what the original symbol requires.
>
> This is the only way to do this in a way so the
> user is actually aware that enabling a webcam also enables USB.
> Or at least this is my best suggestion.
This looks promising.
> But sorry - I have not implemented it.
> And it is likely more complicated than I foresee.
Yeah, in some cases, you can't easily turn on the item depends on
a complex dependency. Distros have similar problems regarding package
maintenance system.
Takashi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists