[R-pkg-devel] Best practice for releasing heavy internal data

[Michael Dewey]

Dear Paul

The advantage of a data-only supplementary package is that users who 
live in countries where they have either a very slow connection or where 
they have to pay per byte to download will be spared 5MB every time you 
update your main package. I do not think the fact that you never expect 
them to explicitly access the data is a worry.

Michael

On 22/02/2019 14:05, Paul Hibbing wrote:
> Hi all,
> 
> I am revisiting this and wondering if it would be a case in which I should
> submit as-is, and include justification for ignoring the NOTE about
> excessive directory size.
> 
> Best,
> Paul Hibbing
> 
> On Mon, Feb 18, 2019 at 3:20 PM Paul Hibbing <paulhibbing using gmail.com> wrote:
> 
>> Hi all,
>>
>> I am preparing a package that makes use of several neural networks,
>> which are quite large. They aren't
>> intended for public use, so they're currently stored in sysdata.R, but
>> they make the R directory too heavy
>> (close to 5MB).
>>
>> What is best practice in this case? I'm aware the general
>> recommendation is to set up a separate data
>> package that updates infrequently, but that seems undesirable since
>> these objects weren't going to be
>> exported in the first place.
>>
>> Thanks for your help.
>> -Paul Hibbing
>>
> 
> 	[[alternative HTML version deleted]]
> 
> ______________________________________________
> R-package-devel using r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-package-devel
> 

-- 
Michael
http://www.dewey.myzen.co.uk/home.html