I would like some rationale on this. For one, I'm not buying the "import" idea. Why? Well I just built HTTPD against the glibc which is also LGPL. The #ifdef #includes make specific allowances for Linux and hence I don't buy that these are "common names for C libaries".2. Can ASF Projects use GPL/LGPL Projects?Yes. But, they cannot distribute them.
ASF projects can use GPL/LGPL code during the build process so long as there is no runtime dependency in the code produced. Programs like checkstyle are OK. Imports of classes covered by GPL/LGPL are not. This last statement needs to be interpreted as a transitive closure. Moving graph from jakarta commons sandbox to werken would not make it OK for Maven to use graph.
While IANAL, the LGPL, as it was explained to me, does not apply unless you directly modify the source of the LGPL library. Meaning if I imported checkstyle, I'd be fine (thats just linking and explicitly allowed), if I go and change even one class, that is not allowed.
What I'd like clarification on is:
1. Is this the result of legal advice?
2. Is this simply a policy decision?
3. Why is it not evenly applied across all Apache projects?
(most specifically HTTPD)
-Andy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
