Forum OpenACS Q&A: Re: Packages and the GPL

Collapse
2: Re: Packages and the GPL (response to 1)
Posted by Talli Somekh on
Assuming that you are writing this package on top of the OpenACS and is statically linked (that is it requires the OpenACS to run):

Steve, if this is an internal package that never gets distributed, then no - it's your package and you do not need to release it.

If, however, you distribute it - sell it or give it - you must pass on the source code and give the receiver all the rights that you have over the code.

talli

Collapse
3: Re: Packages and the GPL (response to 2)
Posted by Bart Teeuwisse on
Talli,

I would think one could license the new package differently than the GPL licensed OpenACS core. The new package doesn't alter the open source OpenACS code and as such is not obliged to make the code of the new package available. I guess this is a matter of semantics. Is the package an extension (and thus alteration) of open source code or is it a new piece of software that happens to require open source software?

/Bart