This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Need Clarification about the Documentation License


> I work in Eclipse and have created hover help for libstdc++ to be
> used in the C/C++ Eclipse editor.
> 
> I took the doxygen output and processed it into a set of Java classes 
> that allows me to look up the documentation for methods.  These Java 
> classes were then Java serialized (put into binary form) so that they 
> could be quickly restored when a user hovers over a particular method 
> (i.e. there is not enough time in a hover request to process the
> data, it must be done prior).
> 
> Reading the documentation license, that binary file is GPL V3 due to
> the inclusion of the doxygen-generated pieces.

Sounds correct to me but I strongly advise getting an actual legal
opinion. Emailed opinons on the internet count for nothing.

Can you give me a
pointer to your work and give me directions so that I can use it
myself? Is this related to GENERATE_ECLIPSEHELP in
libstdc++-v3/doc/doxygen/user.cfg.in?


> The code that accesses the data is EPL (Eclipse Public License) and
> is part of an Eclipse plug-in.  It is not specific to libstdc++, it
> is just using Java serialization to restore Java classes.
> Documentation exists for glibc and newlib, each with different
> licensing.  The location of the serialized classes is given either as
> file within a plug-in, a local file, or a URL.
> 
> At present, I have to keep the libstdc++ binary file at an external 
> location and access it at runtime via URL because Eclipse.org does
> not allow GPL licensed items in the Eclipse repository.  I would like
> the binary to ship as part of a plug-in so the data will be local
> when the user first needs it and web-access won't be required.
> 
> If the binary is provided along with a plug-in as a data file (to
> avoid web access), does the entire plug-in instantly inherit the GPL
> V3 license?
> 
> If no, what is the clause or clauses that specifies this?
> 
> If yes, is it possible to draft a use exception in the license?

I don't know. Sorry.

My desire is to find a way to make this work for you. 

My first pick would be to make this
easy for you and just figure out a way to have the FSF license some
*generated* doxygen docs as GFDL for Eclipse and Debian. Would that
work? Would this work if the generated docs were available for ftp on
gcc.gnu.org?  (Presumably this could then get put into the Eclipse
Repository.)

-benjamin


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]