[email protected] schrieb:
Welche Paragraphen der LPGLv3 auf header-only libs anzuwenden sind und wie, ist doch eine in sich sehr allgmeine Frage, denke ich. Etwas über die Auslegung der FSF ihrer eigenen, kürzlich erst bzgl. header-only libs angepassten LGPLv3 zu erfahren war mein Ziel.Am Dienstag, dem 16. Dez 2008 schrieb FMDSPAM: Gerne. Ich habe bereits Antwort (Frage und Antwort siehe P.S.), auch wenn nicht so, wie ich mir das erhofft hatte. Ich möchte sehr gerne auch eine inhaltliche Antwort an die Entwickler weitergeben, die die Bibliothek unter LPGLv3 gestellt haben. Ich habe zwar bereits deren ausdrückliche Erlaubnis zur Nutzung, Sie interessieren sich aber selbst auch, verständlicherweise, dafür. Sollte da draußen jemand sein, der meine Frage versteht, für allgemein interessant und für (in Grenzen) beantwortbar hält, so möge er sich doch bitte hier melden. Grüße Frank P.S. Auf meine Frage am FSF USA: I develop a closed source, commercially distributed application (not a library if that matters). And I am want use a c++ header-only library. But unfortunately my understanding of the GPLv3/LGPLv3 is to limited to anwser my question myself: "Is it allowed to use work under LGPLv3 (pure c++ header files) in my application without to be enforced to publish any of my application code?". In the Web I found many different opinions about the use of LGPLed Libs in property applications. Mostly saying: "use a dynamic linked version". Which, in itself, is fully understandable and achieve one of the (in my understanding) important goals of the LGPL: To practically enable the combination and usage of the application code with a newer or otherwise changed version of the Lib afterwards without any intervention possible by the original application code creator and vendor. LGPLv3, Paragraph 3 is easy to read and without problems to me. I am confused about paragraph 4 "Combined Works" in regard of header-only libs: Preamble: "Combined Work" is a work produced by *combining* or *linking* an Application *with* the Library. The particular version of the Library with which the Combined Work was made is also called the "Linked Version". So, In my understanding (and please correct me if I'm wrong) the following may be true: *Using* a header only lib, aka producing "object code incorporating material from library header files *is not combining**and therefore not* covered by paragraph 4 "*Combined Works*". works in the the sense of the LGPLv3 My question is: How is LGPLv3,§4 applicable to header-only libraries. Many thanks for your anwsers beforehand. Cheers, Frankerhielt ich folgende Anwort: Thank you for your inquiry about free software licensing. The FSF has offered Free Software licensing support for many years, and has a recognized engineering and legal expertise in this area. As demand and expectation of our service has grown, we require additional funds to support our work. Because of this, we now offer our services by paid consultation to non-free software developers. To answer your questions as outlined, we will require 30 minutes of consultation time, at a cost of $150. If you wish to proceed, please make a payment by credit card at <https://www.fsf.org/licensing/payment/> and e-mail us to let us know that you have done so. We will then send you an e-mail answering your questions, and allow you appropriate follow up. If you prefer to discuss this by telephone, just let us know what times are good for you. If you do not wish to pay for this service, I suggest you carefully review the resources at <http://www.fsf.org/licensing/education> and refer to your legal counsel. Kind Regards, Michael Fötsch |
_______________________________________________ fsfe-de mailing list [email protected] https://mail.fsfeurope.org/mailman/listinfo/fsfe-de
