On Wed, Apr 05, 2006 at 01:20:21PM -0500, D. Hageman wrote:
> If you are going to make changes to the source, you should probably
> do it in a patch and not some perl/sed mojo.

It depends, Dag Wieers had a very good guide on when to do that, you
should check it out.

> If you suggest I take this off list and communicate via private
> channels - I just don't feel like that is very in sync with the open
> source philosophy.

Where did you read that from? I suggested to submit patches to this
list and for John in particular. And to wait for approval before
injecting packages (which even required syntax changes in config
files).

If upstream rejects your submission, you can always diagree with
upstream and do your own stuff, fork, package the fork and whatever,
but in this case, you forked before even giving a chance to discussion
with upstream.

My suggestion is the following: Send in patches for review against the
svn trunk, and make sure it still builds on older platforms. Or if you
can't test it, ask others to lend a hand in testing.
-- 
Axel.Thimm at ATrpms.net

Attachment: pgpMEqcZrCA78.pgp
Description: PGP signature

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

Reply via email to