On Wednesday 12 October 2005 15:39, Axel Thimm wrote:
> On Tue, Oct 11, 2005 at 07:59:34PM +0200, Hans Verkuil wrote:
> > I've removed all duplicates and added a simple way to checkout and use
> > the v4l tree. Read the README.1ST.
> >
> > Testers who can try it on 2.4 are very welcome to do so.
> >
> > Let me know if there are any problems.
> >
> > Warning: it's for development only, don't use in production environments!
> > That's what 0.4.0 is for.
>
> Would it make sense to offer fresh packages of v4l (and linux-dvb, but
> that's off-topic here) and ivtv 0.5.x in ATrpms' bleeding (aka
> experimental) repo?
>
> That way (power) users could check out regressions in the driver and
> have a fast fallback to their 0.4.x driver when they finish their
> tests, you also skip any build user errors on the supported platforms
> e.g.
>
> 1) Hans asks for wide range testing of 0.5.3
> 2) smart channel --enable atrpms-bleeding
> 3) smart update
> 4) smart install ivtv-kmdl-`uname -r` ivtv
> 2) smart channel --disable atrpms-bleeding
> 5) Test test test
> 6) report
> 7) smart install ivtv-kmdl-`uname -r`=1:0.4.0 ivtv=1:0.4.0
>
> Similar for other distributions for which we can coordinate packaging
> of development bits.
Good idea. Once the remaining modules are moved to v4l that would be a good
point for releasing 0.5.0 and making these bleeding edge packages. Given the
breakneck speed at which it's moving right now that point is reached probably
sooned than later :-)
Unfortunately my time is limited this week and next week so I cannot do quite
a much as I'd like to do.
Hans
_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
