To get around this last problem, perhaps you can take advantage of
CRAN's suggestion regarding large data files [1] where they say
"[w]here a large amount of data is required (even after compression),
consideration should be given to a separate data-only package which
can be updated only rarely (si
Dirk Eddelbuettel debian.org> writes:
> On 22 April 2015 at 11:34, Roger Bivand wrote:
> | While I agree with Martyn with respect to code, documentation, and
> | vignettes, the point Ben raises is relevant and not obvious. Data sets in
> | say GLP-licensed packages are on occasion challenged by D
I was assuming that R was configured with --enable-R-shlib but if that's not
the case then you don't need it.
Martyn
> On 22 Apr 2015, at 18:40, Andy Jacobson (NOAA Affiliate)
> wrote:
>
> Hi Martyn,
>
> Thanks for your insight, that seems pretty direct. Unfortunately, I did not
> compile
Hi Martyn,
Thanks for your insight, that seems pretty direct. Unfortunately, I did not
compile this version of R (it's on a large supercomputer system and this
version of R was installed by the admins). Using "R CMD config", I see the
following relevant settings:
DYLIB_LD = icc -std=gnu99
DY
On Tue, 2015-04-21 at 11:46 -0600, Andy Jacobson (NOAA Affiliate) wrote:
> Hi,
>
> I'm encountering trouble compiling caTools_1.17.1.tar.gz and
> e1071_1.6-4.tar.gz on a Linux system using the Intel compiler suite.
> 14 other packages I generally use installed without any trouble. I
> notice both
On 22 April 2015 at 11:34, Roger Bivand wrote:
| While I agree with Martyn with respect to code, documentation, and
| vignettes, the point Ben raises is relevant and not obvious. Data sets in
| say GLP-licensed packages are on occasion challenged by Debian packagers
Not generally the packagers (w
> Jack Howarth
> on Tue, 21 Apr 2015 10:52:52 -0400 writes:
> Is there any plans for addressing the regression...
> https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=15899
> in the 3.2.1 release? In the fink project, I had to resort to creating a
> fixincludes subd
On Wed, 2015-04-22 at 11:34 +, Roger Bivand wrote:
> Martyn Plummer iarc.fr> writes:
>
> >
> > I think this is covered well by the CRAN repository policy:
> > http://cran.r-project.org/web/packages/policies.html
> >
> > The two key license requirements are that:
> > 1) CRAN must have a pe
Martyn Plummer iarc.fr> writes:
>
> I think this is covered well by the CRAN repository policy:
> http://cran.r-project.org/web/packages/policies.html
>
> The two key license requirements are that:
> 1) CRAN must have a perpetual license to distribute the package
> 2) The package license shou
I think this is covered well by the CRAN repository policy:
http://cran.r-project.org/web/packages/policies.html
The two key license requirements are that:
1) CRAN must have a perpetual license to distribute the package
2) The package license should be listed here:
https://svn.r-project.org/R/t
10 matches
Mail list logo
