--- On Thu, 5/13/10, Steven D'Aprano <[email protected]> wrote:
> From: Steven D'Aprano <[email protected]> > Subject: Re: Picking a license > To: [email protected] > Date: Thursday, May 13, 2010, 7:41 PM > On Thu, 13 May 2010 06:24:04 -0700, > Ed Keith wrote: > > > --- On Thu, 5/13/10, Lawrence D'Oliveiro > > <[email protected]_zealand> > wrote: > >> > >> What have you got against LGPL for this purpose? > -- > >> > > Most of my clients would not know how to relink a > program if their life > > depended on it. And I do not want to put then in DLL > hell. So I avoid > > the LGPL. > > > Are you implying that by distributing your libraries under > the MIT or > Apache licence, no linking is required? That's a cool > trick, can you > explain how it works please? > > > > -- > Steven > -- > http://mail.python.org/mailman/listinfo/python-list > Normally I link it for them. As I read the LGPL, if I use any LGPLed code I need to teach the client how to link the software against any possible future version of the LGPLed library. -EdK Ed Keith [email protected] Blog: edkeith.blogspot.com -- http://mail.python.org/mailman/listinfo/python-list
