If I had a proprietary program and wanted to talk to Upstart. I believe I can only link a LGPLed client library into my application, correct? That library most likely has to share atleast header files with a piece of code in the GPLed Upstart Init code so that they share a common message structure and enum definitions.
If those shared header files (shared between the GPLed Upstart Init and LPGLed Upstart Client library) are licensed under GPL, doesn't that contaminate the LPL licensing of the Client library? Sarvi >-----Original Message----- >From: Scott James Remnant [mailto:[EMAIL PROTECTED] >Sent: Friday, June 13, 2008 7:51 AM >To: Saravanan Shanmugham (sarvi) >Cc: Matthias Urlichs; upstart-devel@lists.ubuntu.com >Subject: RE: Upstart Client Library >Importance: High > >On Thu, 2008-06-12 at 13:54 -0700, Saravanan Shanmugham (sarvi) wrote: > >> May be a different way to ask this question is would it make >sense to >> have some of the header files associated with the message/errr >> definitions under the upstart directory LGPLed. >> >> This would make it simpler for people to write other forms of client >> libraries for communication with Upstart? >> >You can use GPL libraries from GPL programs, the library does >not need to be LGPL for you to be able to use it. > >Scott >-- >Have you ever, ever felt like this? >Had strange things happen? Are you going round the twist? > -- upstart-devel mailing list upstart-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/upstart-devel
