After reading the GPL & Libraries, for the first understood more about the definition derived works.
It is not only adding more functionality to a particular open-source code, but also if it is used in combination with another application in the form of libraries ( static and dynamic ).
Then almost all program linking with libc will have to GPL'ed. To avoid this we have LGPL. All system libraries are LGPL, where derived works are not necessarily LGPL'ed.
Further Reading:
http://www.onlamp.com/pub/a/onlamp/2004/11/18/licenses.html
http://www.linuxjournal.com/article/6366
It is not only adding more functionality to a particular open-source code, but also if it is used in combination with another application in the form of libraries ( static and dynamic ).
Then almost all program linking with libc will have to GPL'ed. To avoid this we have LGPL. All system libraries are LGPL, where derived works are not necessarily LGPL'ed.
Further Reading:
http://www.onlamp.com/pub/a/onlamp/2004/11/18/licenses.html
http://www.linuxjournal.com/article/6366
