Explanation for binary files inside source package according to
  http://lists.debian.org/debian-devel/2013/09/msg00332.html

Here is an extract of the response from upstream about
  Files: GenomicRanges/inst/doc/precomputed_results/*.rda
the full response can be read in the log of the ITP bug #721801.

From: Hervé Pagès <hpages@fhcrc.org>
 The objects in precomputed_results can be generated by running the
 code in the OverlapEncodings.Rnw vignette. However running this code
 takes a long time and would make 'R CMD check' take too much time to
 complete, making the maintenance of the package very impractical.
 .
 So the trick is to have some of the more time-consuming code chunks
 in the vignette set to eval=FALSE, and to load the precomputed results
 instead. The loading is performed in a hidden code chunk and it also
 performs some sanity checks to verify that the precomputed object that
 was just loaded is in sync with other objects generated earlier in the
 vignette.
 
From: Martin Morgan <mtmorgan@fhcrc.org>
 For precomputed_results above, it looks like these could be generated by a 
 script, but the specific results depend on a web service query and the web 
 service changes from time to time. So the script will become out-of-date, 
 creating data that are no longer consistent with the illustrative puruposes of 
 the vignette. Also, the time cost of generating data is not consistent  with our 
 (nightly) build process; we will not generate this data on the fly, and it would 
 be a mistake for your release process to generate data different from the data 
 used in our release. These (expense of computation, consistency of external data 
 sources) are typical reasons.

 -- Andreas Tille <tille@debian.org>  Fri, 18 Oct 2013 10:34:02 +0200

