From: Mart Raudsepp <leio@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: Remove USE="v4l2" and rename the consumers to plain USE="v4l"?
Date: Fri, 20 May 2011 13:02:28 +0300 [thread overview]
Message-ID: <1305885748.17955.14.camel@localhost> (raw)
In-Reply-To: <4DD1C5D7.4090502@gentoo.org>
On T, 2011-05-17 at 03:48 +0300, Samuli Suominen wrote:
> And after the bugs are mostly (or all) dealt with, I suggest we remove
> USE="v4l2" and make USE="v4l" mean:
>
> "Enable support for video4linux (with or without userspace library libv4l)"
>
> And rename the pkgs using USE="v4l2" to USE="v4l". Since there will be
> only video4linux version 2, using libv4l or without (or possibly using
> libv4l compability layer for libv4l1). But no more straight up version
> 1 support since videodev.h is gone since Linux 2.6.38
I think for a while people would read "v4l" as "v4l1", as v4l did denote
version 1. Any reason not to congregate everything to USE="v4l2"
instead?
--
Mart Raudsepp
prev parent reply other threads:[~2011-05-20 10:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 0:48 [gentoo-dev] RFC: Remove USE="v4l2" and rename the consumers to plain USE="v4l"? Samuli Suominen
2011-05-17 1:36 ` [gentoo-dev] " Duncan
2011-05-20 10:02 ` Mart Raudsepp [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1305885748.17955.14.camel@localhost \
--to=leio@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox