> Hmmm.... I put a GPL notice in the PlrkData source code (which I did put
> up on my site) but didn't put any licensing on an installer or the program
> itself. Do I need to?
If your code is GPL, you merely need to include a copy of the
license, generally called COPYING or LICENSE or some such in your publically
distributed package. If your package includes both binary and source, that's
sufficient (along with COPYING). If it does not, you must provide
"equivalent access" to the source, at the same level as the binaries, along
with a copy of the license. You do not need a "clickwrap" or "clickthrough"
license.
It also helps (you and others who may wish to incorporate your code)
if you slap a GPL header at the top of each of your source files, so there
can be no question as to what type of license each file is under. Example:
in pilot-link, a package I maintain, there is a mix of licenses, mostly GPL
and LGPL, but the distinction between the userspace tools (which are GPL)
and the core libraries (which must remain LGPL) had to be made clear in
_each_ file, so that people linking to them would know how to treat their
own code.
Just my 0.02 Euros.
d.
_______________________________________________
plucker-list mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-list
