Re: Semi-automatic upgrades to new upstream versions (Was: Upcoming Bioconductor 3.7 release, developed for R 3.5.0)
Hi Andreas,
2018-04-24 8:52 GMT+02:00 Andreas Tille <andreas@an3as.eu>:
>> I think after further testing of
>> others and thorough inspection of the results we might move it over to
>> the dh-r package.
>
> What do you think about this?
>
Thanks for this, yes this will be useful as well for the
create_README.source script. I have just two comments:
1. For the routine-update script:
I think it's not necessary to check if debian/tests exists to add
Testsuite: autopkgtest-pkg-r into d/control.
If I remember well, when both are present (Testsuite:
autopkgtest-pkg-r and some tests into debian/tests), only tests into
debian/tests are executed (I will check it).
As I am working to improve autopkgtest-pkg-r (and make useless common
tests in debian/tests), the "Testsuite: autopkgtest-pkg-r" field could
always be present into d/control so we will only have to remove tests
from debian/tests in favor of autopkgtest-pkg-r.
2. For the create_README.source script:
As suggested by lamby [1], it could be useful to have a more
machine-readable format than the current README.source.
It should not a big deal but we have to agree on which format do we
want, then just let your script do the job to fill the file.
Maybe we can take this opportunity, to make this file more general and
not only useful for RData files. i.e. by adding information about
other binary data, I'm thinking about feather data files [2] for
example.
Best,
Dylan
[1] https://bugs.debian.org/891231
[2] https://cran.r-project.org/package=feather
Reply to: