Hello, there
I am happy to see, that I am not alone.
There is a problem, if you are doing something that you had to distribute and
you are not able to distribute the source code (some reason or other).
Then our problem level is serious with GPL.
> Of course, since Perl programs are typically in source form anyway, I
> fail to see what kind of limitation we are talking about.
> Abigail
Even if Perl is script language, there are programs
which can compile your Perl code to binary and then you have to consider if
you had to release your source code or not.
I'm sure that there are plenty of modulemakers who don't think the
license options so far, that they could see how the choosen license
works in practice. They choose GPL because it's so common and popular.
I think that people who are doing modules enjoy
programming and like to help others.
The following formula is the one that requires too much energy:
-----------------------------------------------------------------------------------------------
- Not use the module
- try to search optional module
- invent the wheel again
- try to discuss with the author about special license
- try to find some holes in license agreements
-----------------------------------------------------------------------------------------------
Because I personally like programming Perl and not investigating the license
acreements I hope that we are able to get some allowance to this.
Is there anything, that we can do to make this at least a little bit easier ?
(so, that we could concentrate more to the programming :) )
Regards,
Sami
