Re: packaging RProtoBuf: permissions only patches?

[Jonathon Love <jon@thon.love>]

thanks for getting back to me dirk, responses below

On 21/04/2016 20:48, Dirk Eddelbuettel wrote:
> On 21 April 2016 at 20:18, Jonathon Love wrote:
> | my next hurdle is to do with tests. normally, the contents of an R
> | packages tests directory ends up in /usr/share/doc/$packagename/tests
> |
> | so in this example:
> |
> | http://anonscm.debian.org/git/debian-science/packages/r-cran-rprotobuf.git/tree/tests
> |
> | i'd expect `runUnitTests.R` to turn up in
> |
> | /usr/share/doc/r-cran-rprotobuf/tests
> |
> | however, this doesn't happen. i usually begin a package by copy/pasting
> | an existing one, so i'm quite puzzled by this.
> |
> | any suggestions as to what i'm doing wrong?
>
> The R package has
>
>     tests/runUnitTests.R
>
> calling out to the files in
>
>     inst/unitTests/
>
> which became
>
>     unitTests/
>
> in the installed package.  But they need their test driver -- but
> runUnitTests.R is not installed by R CMD INSTALL.  That's just how it is.
yeah, that makes total sense. but i'm trying to understand how other 
packages get their tests copied into /usr/share/doc/$packagename/tests

so for example, r-cran-afex has tests in it's root directory:

http://anonscm.debian.org/git/debian-science/packages/r-cran-afex.git/tree/tests

and these turn up in /usr/share/doc/r-cran-afex/tests :

https://packages.debian.org/sid/amd64/r-cran-afex/filelist

?!

> I'd just skis this here.  The package _does_ tests its installabilty during R
> CMD INSTALL by loading itself.
yeah, i'm more than happy to just rely on the package loading test, but 
this seemed like a good opportunity to expand my understanding of what's 
going on.

with thanks

jonathon