BTW, ask IBM how they'd feel about having to make their products licensed with the section 6 restrictions. That would make POI unusable for them for instance. In any case this is a moot point. The board wouldn't allow us to distribute with this restriction. (I'd veto even if they didn't but they're very clear on this anyhow)
-andy On 7/16/03 3:19 PM, "Ryan Ackley" <[EMAIL PROTECTED]> wrote: > >> DT: >> This sort of linking falls under section 6 of the LGPL. > > Andy, I'm confused because section 6 is the section that states > "...distribute that work under terms of your choice, provided that the terms > permit modification of the work for the customer's own use and reverse > engineering for debugging such modifications" I would interprete DT's > response as saying that we CAN link to LGPL code because the Apache license > fits this requirement. I haven't been able to find anywhere in section 6 > that says we have to make something that links to LGPL use the LGPL license. > > I am interested in hearing your reasons for interpreting section 6 this way. > It actually is the section that gives permission for linking to LGPL code > with NO restrictions except that you have to do one of the following > > 1)distribute the source of the Library if you distribute the Library. > 2)Provide the ability to link to the library that already exists on the > users computer at runtime (java already handles this). > 3)blah blah blah > 4)blah blah ... > > You get the point. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -- Andrew C. Oliver http://www.superlinksoftware.com/poi.jsp Custom enhancements and Commercial Implementation for Jakarta POI http://jakarta.apache.org/poi For Java and Excel, Got POI? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
