Use of LGPL images in proprietary software?

Lawrence Rosen lrosen at rosenlaw.com
Mon Oct 5 15:01:34 UTC 2009


John Cowan wrote:
> So either you need to ship an editor that can modify your executables, 
> or you need to make them separate, perhaps as separate files or in a
zipfile.

Where does the LGPL impose that burden? 

/Larry



-----Original Message-----
From: John Cowan [mailto:cowan at ccil.org] 
Sent: Monday, October 05, 2009 7:51 AM
To: Mala Dibbs
Cc: license-discuss at opensource.org
Subject: Re: Use of LGPL images in proprietary software?

Mala Dibbs scripsit:

> i found an icon set licensed with LGPL which I would like to use in
> proprietary (and potentially commercial) software.
> 
> 1. Can I use the images at all?

Yes, you can.

> 2. Can they be embedded in binary files (e.g. statically linked into
> the executable) or do they need to be accessible for the user?

They need to be readily replaceable by the user.  This does not mean
that if the user replaces them with unsuitable images (wrong format,
wrong size, whatever) that your program has to still work.  It means
that if a new version of the images becomes available, the user can
easily plug them into your software.

So either you need to ship an editor that can modify your executables, or
you need to make them separate, perhaps as separate files or in a zipfile.

> 3. Can I modify them?

Yes, certainly.

> 4. Am I right, that modified versions will be LGPL again and that I need
> to ship a License text with the Images (regardless of modifications)?

Yes.

> 5. Is it correct, that the software itsself does not need to be open
> source or free software if I use these images?

That is correct.

I am not a lawyer, and this is not legal advice; however, it is not the
unauthorized practice of law, either.

-- 
Not to perambulate                 John Cowan <cowan at ccil.org>
    the corridors                  http://www.ccil.org/~cowan
during the hours of repose
    in the boots of ascension.       --Sign in Austrian ski-resort hotel






More information about the License-discuss mailing list