Re: [Tutor] Regarding licensing GPL terms

2007-01-31 Thread Kent Johnson
Kent Johnson wrote: > Anup Rao wrote: >> c> Also, does any python script that uses this module have to be >> distributed under GPL , LGPL, or is the PSF license sufficient? >> My preference would be the PSF but I am not sure if it is ok. > > The PSF itself discourages using the PSF license f

Re: [Tutor] Regarding licensing GPL terms

2007-01-31 Thread Terry Carroll
On Wed, 31 Jan 2007, Anup Rao wrote: > Hi, > > I am writing an application that uses a python libary (a *.so file) > generated using SWIG. > This library makes direct system calls to the Linux kernel. The Linux kernel is not actually licensed under the standard GPL. The copy of the GPL Lin

Re: [Tutor] Regarding licensing GPL terms

2007-01-31 Thread Andrew Ball
Cool! Do you know about rpath/conary? It may not be worth tons here, but it is good for custom Linux distributions. http://www.rpath.com/corp/ On 1/31/07, Anup Rao <[EMAIL PROTECTED]> wrote: Hi Andrew, A minor correction in the URL it is *http://sarovar.org/projects/pylinux/* Sorry for

Re: [Tutor] Regarding licensing GPL terms

2007-01-31 Thread Kent Johnson
Anup Rao wrote: > > Hi, > > I am writing an application that uses a python libary (a *.so file) > generated using SWIG. > This library makes direct system calls to the Linux kernel. > This raises three questions. > > a> Does this mean that the library must be distributed under GPL terms? I d

Re: [Tutor] Regarding licensing GPL terms

2007-01-31 Thread Michael Lange
On Wed, 31 Jan 2007 13:34:24 +0530 Anup Rao <[EMAIL PROTECTED]> wrote: > Hi, > > I am writing an application that uses a python libary (a *.so file) > generated using SWIG. > This library makes direct system calls to the Linux kernel. > This raises three questions. > > a> Does this mean that

[Tutor] Regarding licensing GPL terms

2007-01-31 Thread Anup Rao
Hi, I am writing an application that uses a python libary (a *.so file) generated using SWIG. This library makes direct system calls to the Linux kernel. This raises three questions. a> Does this mean that the library must be distributed under GPL terms? b> Can I distribute it as LGPL? c> A