On 9 October 2015 at 16:12, Laurent Gautier wrote:
| Building the doc is not that hard (I am building it all the time). The doc to
| do it is just patchy.
| 
| The most centralized source of information might be interested here:
| 
https://bitbucket.org/rpy2/rpy2/issues/293/fix-and-do-regression-tests-for-docs
| 
| Otherwise, the dynamic part are beginning to also be checked in version
| control, so the doc builds on readthedocs. Building it the same way should be
| as easy as "make html" or "make latexpdf" when starting from a clone of the
| repos.

I no longer build from the repo [as that process went belly-up for reasons I
longer recall; maybe after yet another repository move of yours or some other
reason] but just use the source tarball.

Would there be another (simple!!) way to build the documentation?  As I don't
use rpy2 myself, I have somewhat limited motivation in chasing this down.

rpy2 2.7.1 is now Debian, a little more delayed than usual as I was out of
the country for a bit.

Dirk

 
| L.
| 
| P.S.: Enjoy Tokyo.
| 
| 
| On Thu, Oct 8, 2015, 6:32 PM Dirk Eddelbuettel <[email protected]> wrote:
| 
| 
|     On 8 October 2015 at 21:56, Julien Puydt wrote:
|     | Package: python-rpy2
|     | Version: 2.7.0-1
|     | Severity: wishlist
|     |
|     | Hi,
|     |
|     | first, the binary python-rpy2 package suggests python-rpy-docs which
|     | doesn't exist (python-rpy-doc does, but it's for the previous version!).
|     |
|     | Could you please ship a python-rpy2-doc package?
| 
|     I have in the past, but Laurent used to either drop documentation, or
|     require
|     pieces we don't have, or create other issues for. I was otherwise always a
|     big fan -- forst project where I saw sphinx in action way back when.
| 
|     Laurent, what do I need for 'make doc' these days?
| 
|     Greeetings from Tokyo,  Dirk
| 
|     |
|     | Thanks,
|     |
|     | Snark on #debian-python
| 
|     --
|     http://dirk.eddelbuettel.com | @eddelbuettel | [email protected]
| 

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | [email protected]

Reply via email to