So surely what we need then is a statement that as of 0.6 (or whatever it's called when it is released) ivtv is compatible with kernel 2.6.xx (15?) or requires this release of v4l2. This would of course mean that probably we would want a kernel & v4l2 release to happen before we can release ivtv 0.6 though. I don't see how we can succesfully release against a development branch of v4l2 or maybe i've just missed something.
John --- Tyler Trafford <[EMAIL PROTECTED]> wrote: > On Wed, Nov 09, 2005 at 09:27:32AM -0500, Axel Thimm > wrote: > > > No offence to v4l code! Every code has to go > through development and > > its cvs/svn/etc developement area will be > bleeding, same goes for > > ivtv. But having this dependency means that ivtv > would be able to > > release a stable 0.6.x only if there will be a > stable v4l release > > containg the required modules, too. Or otherwise > ivtv 0.6.x will build > > on Mondays and fail on Tuesdays depending on the > state of v4l cvs. > > There's a distinction to be made now between 'ivtv' > and modules that ivtv > happens to load. ivtv releases for any >0.4.0 > branch will not contain > the support modules. > -- > Tyler Trafford > > _______________________________________________ > ivtv-devel mailing list > [email protected] > http://ivtvdriver.org/mailman/listinfo/ivtv-devel > _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
