On Fri, 18 Nov 2005 12:29:05 +0100
Nils Faerber <[EMAIL PROTECTED]> wrote:

> Well, to correct myself a little, yes, there is a small infringement...
> they would have had to mention the use of LGPL code.
> That would be a nice thing in new Sony-CD-booklets: "This product
> contains parts which are covered under the GPL/LGPL" ;)
> 
> All other claims are easy to handle by Sony: They send you the objects
> files and point you to lame.sf.net for the source.

Regarding the LGPL: anyone using the product has to have the
possibility to generate the the same executable somehow. The easy way
to accomplish this is to have the LGPL part as a library.

The XCP issue at hand doesn't work that way, the library isn't provided
as a dynamic link object, it's embedded into some other files. So to
make it comply to the LGPL you have to be able to get the same
development tools somehow (so either use standard development tools, or
provide all of the in-house tools used), and a way to "clue" the LGPLed
object files you generated on your own to the product.

Since I'm one of the maintainers of LAME: the above paragraph is just
an poor mans interpretion of the LGPL as I understand it. I'm no
lawyer, I didn't consulted a lawyer to get the LGPL explained, and
everyone who wants a legal view of the LGPL should contact the FSF, a
lawyer or any other appropriate person. Providing my interpretion of
the LGPL doesn't expresses any upcoming actions from the LAME
maintainers, it is just a "I think you got something wrong, I think
it's more like ...".

Regarding the topic of this thread: the LAME maintainers are discussing
the XCP issue internally. We make a public announcement about our
decision ASAP.

I suggest to not try to read something between the lines in this
message, since this message doesn't provide a preview of our
announcement or our intentions. It just allows to say that we will make
an informed decision, whatever it will be.

Bye,
Alexander.

-- 
http://www.Leidinger.net                       Alexander @ Leidinger.net
  GPG fingerprint = C518 BC70 E67F 143F BE91  3365 79E2 9C60 B006 3FE7
_______________________________________________
mp3encoder mailing list
[email protected]
http://minnie.tuhs.org/mailman/listinfo/mp3encoder

Reply via email to