Chris, perhaps you can talk to Mike and get clarity on this. If they aren't willing to do so, then I don't think it is a good idea to continue modifying our script to accommodate their driver updates. But obviously it's ideal it they keep them as is. Talking to Greg, I got the impression that adding ephiphan only involved a few simple steps. I didn't get the impression that it would leave people in the cold. imho, adopters that are interested in building a box from scratch would be open to doing these additional steps. On a separate note, installers already need to request new drivers from Epiphan if they're running a new kernel, so the current experience already isn't ideal.

Thanks Greg for adding a patch.

On 2/25/11 8:18 PM, Christopher Brooks wrote:
I think we should start by telling them the impact of this; that out of
the box someone will need to configure things to work with their card.
They might agree to quit changing things to make it a bit easier on
us...

(this would be my preference over leaving people in the cold to "just
figure it out", especially if they keep changing it and we have just a
documentation/support nightmare)

(is there a ticket for this?)

Chris

Epiphan has yet again changed their drivers (which means we need a
1.0.3) and will likely need to react to this modifications into the
unforeseeable future.  It seems like you don't need to be a rocket
scientist to manually install epiphan and that it only demands some
minor additions to the docs.  imho, folks interested in building
their own capture agents already have the mind set to take these
additional steps. thoughts?

~Adam
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn


To unsubscribe please email
[email protected]
_______________________________________________


_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn


To unsubscribe please email
[email protected]
_______________________________________________

Reply via email to