Actually I think we could make our lifes much easier by having better build systems! So we would only have the Apache code in out repositories and let the build system get the external dependencies for us. AFAIK this should save us from legal troubles.
No, not necessarely. The problem with LGPL is that it doesn't define (in java) where the library stops and where your program starts. Having it downloaded from another machine, doesn't change that at all.
Hm... but the question is: if something relies on something terms of *uses* it's API does this make it a problem? I mean that would be really like a viral infection! You couldn't even connect to software that is under (L)GPL. (What about protocols?)
Is it really like that? I mean: how does it work for the PHP guys with all the modules and libraries then?
In the case of GPL, it is clear and works as you fear above. Protocols (such as XML RPC or SOAP) are fine.
ISTR code being removed from PHP due to such considerations, but it has been a while since I have been involved with that project.
- Sam Ruby
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
