[R-pkg-devel] .tar vs. binary builds

[Ben Bolker]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 15-08-03 04:31 PM, Glenn Schultz wrote:
> Hello All,
> 
> I have a package which I would like to distribute.  However, there
> are some classes that are not exported if I provide a tar file can
> the user decompress the tar to the source and then export class.  I
> am thinking the answer is year since the tar is source code.
> Conversely, a binary build would prohibit this - correct?
> 
> Best Regards, Glenn ______________________________________________ 
> R-package-devel at r-project.org mailing list 
> https://stat.ethz.ch/mailman/listinfo/r-package-devel

  Not really clear what your question is.  If you distribute a source
package/'tarball' (i.e. .tar, typically compressed to .tar.gz) then
users can install via R CMD INSTALL [...] or within R
install.packages("...",repos=NULL).  Then they'll have access to
everything that is exported via your NAMESPACE file.  Can you be more
concrete/specific/clear about what you have in mind?

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEcBAEBAgAGBQJVv9KLAAoJEOCV5YRblxUHnokIANorhDR3olkH3zLlt9ZoYMS+
uNuVfRuF9JOhe2BD0C4fEUEkPp0IjnNNcDdP1R6gBSaj8ai+Lq2qOKucwPpll6zr
9q+5jUxKaQJmO6QBzMJODSSflFjZmbwZHhb0QLzDMfn41cAcg18K0uW6SLH91avF
kqPxVGn2sAccBuZtjbjCdPfRHalg/N0rSmvgWDNTtVQhbZJFfAwopgVqVyMKm2wV
K+J2xGd85NAkHCT/1No0ghG5s6/GTXjsfD0O5qJ07Ut5/GwLaWkeS9F9fEHPvziC
XlwOjsaOg8YNpCWi2aycrQYt9zINNTmFsN0Zrg/k+x2Zuoim9QeTHdWnWT8K85I=
=enco
-----END PGP SIGNATURE-----