I'd like to have a version of a package that doesn't include sources. I
thought that this could be achieved by using binary option in R CMD build,
but in fact it packages source code that could be easily printed once the
library is loaded. Is there an option to avoid visibility of the source?
On 11.10.2011 18:33, A Zege wrote:
I'd like to have a version of a package that doesn't include sources. I
thought that this could be achieved by using binary option in R CMD build,
but in fact it packages source code that could be easily printed once the
library is loaded. Is there an option
On 11/10/2011 12:33 PM, A Zege wrote:
I'd like to have a version of a package that doesn't include sources. I
thought that this could be achieved by using binary option in R CMD build,
but in fact it packages source code that could be easily printed once the
library is loaded. Is there an option
OK, gentlemen, i agree with you in general. I was not talking about a general
purpose, general use package that one prepares for CRAN. I am sure you are
familiar professionally or can imagine situations where you need to
demonstrate a solution to a specific task without fully disclosing the
On Oct 11, 2011, at 1:09 PM, A Zege wrote:
OK, gentlemen, i agree with you in general. I was not talking about a general
purpose, general use package that one prepares for CRAN. I am sure you are
familiar professionally or can imagine situations where you need to
demonstrate a solution to a
One of the most secure options, I think, is to provide a
web-based tool to do the computations. I know one case where this was
done. The clients probably did not even know that R was being used to
do the computations. They had an application or a procedure for
uploading their data to
On Tue, Oct 11, 2011 at 6:09 PM, A Zege andre.z...@gmail.com wrote:
OK, gentlemen, i agree with you in general. I was not talking about a general
purpose, general use package that one prepares for CRAN. I am sure you are
familiar professionally or can imagine situations where you need to
