[R-pkg-devel] .tar vs. binary builds
bbolker at gmail.com
Mon Aug 3 22:43:55 CEST 2015
-----BEGIN PGP SIGNED MESSAGE-----
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
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)
-----END PGP SIGNATURE-----
More information about the R-package-devel