On Tue, 4 Apr 2006, D. Hageman wrote:

> On Tue, 4 Apr 2006, John Harvey wrote:
>>>
>>> I think this is something you first have to discuss with
>>> upstream and get their go before publishing such modified
>>> code and even packaging it for broader consuming. I'm sure
>>> John, who's the maintainer of the xdriver will listen to any
>>> suggestions you have.
>>>
>>> I'm not saying that the changes are bad. It is just not the
>>> way oss works, unless you want to fork the project. If you
>>> really want to fork then please use another versioning, the
>>> current state will only confuse users. Otherwise please feed
>>> this list with little patches that can be reviewed. Thanks.
>>> --
>>> Axel.Thimm at ATrpms.net

I have posted a new version of the RPMs at 
http://people.eecs.ku.edu/~dhageman/rpms/

This version should be a compatible with pre-existing X configurations. 
The only change is that the driver is called ivtvdev_drv.so to keep it 
consistent with all of the other X drivers.

This rpm was made by taking the ark driver from RedHat and switching the 
source code with the ivtv X driver.  The autotools was updated to handle 
the new file names.  This is what is in the new tarball.

A patch of the changes I applied to the ivtv X driver source code to make 
it build in this configuration is in a separate file in the SRPMS.

I didn't take the time to do this initially as I didn't know if there was 
any demand for this type of rpm.  Now that I have been receiving mail from 
people who are finding it useful, I feel like I should polish them up a 
bit.

This should make it easy to continue to develop and distribute the ivtv X 
driver like it is now, but still package RPMs that can be used on 
RedHat/Fedora-type systems.

Again, I have no desire to fork anything.  I just found the current state 
of ivtv rpms didn't meet my needs and felt that I could help other people 
who felt the same way.

-- 
//========================================================\\
||  D. Hageman                    <[email protected]>  ||
\\========================================================//

_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

Reply via email to