OK, Java-specific question. It seems likely that altering or inlining LGPL code pollutes the Apache license. Are you of the opinion that IMPORTING but not altering or distributing LGPL classes pollutes the Apache licecnse? And if so, can that be stated on the Wiki page? If LGPL code cannot be imported, it's pretty much useless in any capacity for Java projects.
- Morgan --- Rodent of Unusual Size <[EMAIL PROTECTED]> wrote: [snip] > i'm not even going to touch the infection issue at > this point; > it always makes my cephalic nodule hurt horribly. > let's > just say that we can't do anything that will trigger > an > infection of the asf's assets -- or those of someone > using > asf packages. if a licence permits *linking* > against > a library, there's no prohibition on our packages > requiring > the library in order to run properly. if a licence > allows > us to include the library, as a general rule we can > package > it with our stuff. if by linking with it or > including it > in our distributions we trigger a clause in its > licence that > either overrides the asf licence on our stuff, or > forces > the user to comply with rules more restrictive than > the > asf licence.. then we mustn't do that. [snip] ===== Morgan Delagrange http://jakarta.apache.org/taglibs http://jakarta.apache.org/commons http://axion.tigris.org http://jakarta.apache.org/watchdog __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
