2008/6/10 Gregory Warnes <[EMAIL PROTECTED]>:
>
> Well, unless/until we change the implementation, I think the rpy package
> really must match the exact version*s* of R it was compiled againts.

It does, but because I think this is enforced by name mangling of the
C-written python
module rpymodule*. If the R symbols used in rpy do not change across a stretch
of R releases, I think that the same compiled code could be used.

For rpy2, I am planning / would like to have it changed (point b- in
earlier email).

> Note, however, that RPy is designed so that one can compile against several
> version of R so that a single package can support multiple R versions.

The issue encountered is that when a new version of R is released, a
new compiled rpy package must be released as well.
Would a documentation stating "good from R-x til R-y / beyond R-y run
the checks provided" be acceptable ?
(a warning issued at runtime can also be considered)


> -G
>
>
> On Jun 9, 2008, at 1:12PM , Dirk Eddelbuettel wrote:
>
> On Mon, Jun 09, 2008 at 12:36:19PM -0400, Gregory Warnes wrote:
>> Aside,  since rpy _does_ check for specific R versions, would it not be
>> advisable for the .deb dependencies to reflect this appropriately?
>
> I tried that for a while but discontinued because it can lead to
> upgrade blocks just because a particular hardware platform doesn't yet
> have its rpy version.
>
> So 'in theory, yes; in practice, didn't work', at least when I tried.
>
> For the r-cran-* packages, I settled on using a Depends on '>=' the R
> version I built with.  Would that be a possibility here?  Or do you
> think you really need the equality?
>
> Dirk
>
> --
> Three out of two people have difficulties with fractions.
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> rpy-list mailing list
> rpy-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/rpy-list
>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> rpy-list mailing list
> rpy-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/rpy-list
>
>

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
rpy-list mailing list
rpy-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rpy-list

Reply via email to