<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=Content-Type content="text/html; charset=us-ascii"> <META content="MSHTML 6.00.5730.11" name=GENERATOR></HEAD> <BODY> <DIV dir=ltr align=left> </DIV> <DIV>Good point... well, I guess we've lived with it this long... ;-)</DIV> <DIV> </DIV> <DIV> </DIV> <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left> <HR tabIndex=-1> From: crash-utility-bounces@redhat.com [mailto:crash-utility-bounces@redhat.com] On Behalf Of Dave Anderson Sent: Wednesday, December 13, 2006 5:32 AM To: Discussion list for crash utility usage, maintenance and development Subject: Re: [Crash-utility] Crash extensions and GPL </DIV> <DIV></DIV>Castor Fu wrote: <BLOCKQUOTE TYPE="CITE"> Would it be possible to modify the license for crash so extensions would not be subject to the GPL? Our developers create extensions which use our proprietary source code, and while they are most useful in-house, it'd be nice to be able to ship them to customers. </BLOCKQUOTE>I am not a lawyer, nor am I an open source zealot, but the crash utility is subject to the GPL due to the embedded gdb module. Given that any extension would be in all probability require a gdb service, how could you work around that? Dave <BLOCKQUOTE TYPE="CITE"> We're certainly interested in contributing back generically useful code, but this would be a 'nice to have'. I'm not a lawyer, so I'm not sure how to modify the license, but I could ask people here for help if this seems reasonable. -castor <PRE WRAP><HR width="90%" SIZE=4>-- Crash-utility mailing list Crash-utility@redhat.com <A href="https://www.redhat.com/mailman/listinfo/crash-utility">https://www.redhat.com/mailman/listinfo/crash-utility</A></PRE></BLOCKQUOTE></BODY></HTML>