[R] Making a trial based Package for 30-days.

Spencer Graves spencer.graves at structuremonitoring.com
Mon May 12 16:45:08 CEST 2014


On 5/12/2014 7:28 AM, Barry Rowlingson wrote:
> On Mon, May 12, 2014 at 1:11 PM, Ashis Deb <ashisdeb83 at gmail.com> wrote:
>> Well  it's  the company requirement to do  so  ,  and  give it on  a trial
>> basis  to  client to check , if they  like they  will BUY  or  it will  self
>> destruct itself ,
>   No, if they like it they will BUY or they will CIRCUMVENT your
> self-destruction mechanism.
>
>   The company requirement has not been thought through to
> practicalities, and is unrealistic, and is not constrained by
> limitation. How do you prevent them re-installing?
>
>   For a price, I will fly (first class) to all your clients after 30
> days and delete the software for you.


       Linux is free, open source software (FOSS), but people create 
lots of commercial software to run on Linux.


       One company I know installed an S-Plus or R package only on 
servers, so their customers had to use it on a server.  (In this case, 
the customers had a GUI and may not have known that it was S-Plus or R 
behind it.)  This company also developed techniques for encrypting their 
code.  I don't think it was perfect, and they eventually wrote it in C 
or C++ or Matlab.


       So part of the answer is you can write part of your package in a 
compiled language.  That part can check your web site to check the date 
and other things.


       If you submit anything to CRAN, you must enter a legally binding 
agreement that anything you submit is released under an acceptable FOSS 
license.  I don't know what they do if they find an unacceptable license 
in a CRAN package, but at minimum, the package will be removed.


       Spencer

> Barry
>
> ______________________________________________
> R-help at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-help
> PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
> and provide commented, minimal, self-contained, reproducible code.



More information about the R-help mailing list