Re: [rdiff-backup-users] win32 error 126

[Greg Freemyer]

On Tue, 2003-11-11 at 15:25, David Kempe wrote:
> ----- Original Message ----- 
> From: "Greg Freemyer" <address@hidden>
> > 1) All code that calls cygwin.dll must also be gpl.  (rdiff-backup
> > qualifies.)
> > 2) The source code for cygwin.dll must be made available to end-users
> > (for 5 years??) by anyone distributing cygwin.dll.
> >
> 
> rdiff-backup is GPL as well, so if I write an application that is a frontend
> to rdiff-backup and just executes rdiff-backup with options ( I guess it
> calls rdiff-backup), would I need to release that source code under the GPL
> as well?
> Like a gui or web based frontend to rdiff-backup, would that need to be GPL
> as well?
> 
> dave
Dave,

IANAL,

I believe that question is heavily addressed on the GPL faq, and is
worth your time to lookup and verify what I am saying.

--
My understanding is that if you link (staticly or dynamicly) to a
library and the library is GPL, your app must be GPL.

If you invoke an app via the exec command, then your app does NOT need
to be GPL.

FYI: Many libraries are licensed via the LGPL.  I believe the LGPL is
targeted specifically at libraries and allows non-GPL programs to link
to them.  Cygwin has specifically chosen not to use this approach.

librsync uses the LGPL.

Greg
-- 
Greg Freemyer