A client of mine has asked me to investigate the possibity of licensing an application they have written in Perl.
From my days of working in licensing, the only solution I've used for licensing scripts is to put some vital application function in an external shared library, written in C, or something which is then licensed. Thus, in order to use the scripts which need this function, the license requirements have to be met.
I note that presently, the application is written to work on multiple platforms.
I can think of no other way of solving this problem other than to supply a complied library for each platform, and having an associate perl module which calls it.
So, my questions are these:
Is this the way that other people do it, or is there some better way?
Are there any caveats associated with supplying multiple compiled libraries with perl modules, assuming some install script is made to choose the right one?
--
Steve Marvell
In reply to licensing perl code by marvell
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |