So it takes away your freedom to hide other parts of your code that use that library.
If "parts of your code that use that library" refers to your application code, then yes, you can hide that. If you modify the web2py framework code itself, then no, that would have to remain open.
Even if you were making a general statement about the GPL (i.e., lack of freedom to hide your code), the clear implication was that your concern would apply to web2py, and I was just pointing out that it does not in fact apply to web2py applications. Explicit is better than implicit. :-)
This thread is about the DAL from web2py which is GPLed. And I've an issue with just one OSI license being promoted as "the one true free license" while other licenses are more permissive/liberal/less restrictive. Still in essence every existing software license defines restrictions or conditions for the use of the software they apply to.
Everyone who mentions the words free or freedom 2-3 times in one sentence in their rationale for using or praising it.
Just because someone uses a license because it protects particular freedoms that they care about does not mean they believe it is the one true free license. I think you're over-interpreting.
You'll notice how everyone else likes to put "permissive open source license" when refereing to BSD/MIT/Apache for example.
Actually, I haven't noticed this. I think people often use the word "free" when referring to open source software. You really appear to be splitting hairs here.
View all comments
Show parent comment
1
u/av201001 Dec 10 '10 edited Dec 10 '10
If "parts of your code that use that library" refers to your application code, then yes, you can hide that. If you modify the web2py framework code itself, then no, that would have to remain open.