> On 06/30/10 07:30 PM, Mariah Lenox wrote: > > The spkg r-2.10.1 includes inside it the spkg rpy2-2.0.8. > > > > According to the relevant SPKG.txt, r-2.10.1 comes from > > http://www.r-project.org/, while rpy2-2.0.8 comes from > > http://rpy.sourceforge.net/rpy2.html. > > > > Is it policy to put a sage package inside another sage > > package ... or would it be better to put them both at > > the same level with a note about the dependency > > in the deps file? > > > > Mariah > > I noticed is recently - I'm not sure how recent it is. > > I think its a bad idea. Especially now we have the ability to build > packages in parallel, it would make more sense to split packages than to > combine them. > > Was there ever a good reason for combining these? > rpy has been in the R spkg for a long. Although I think when I started working on sage there was a copy inside R and one outside. For more of these look at sagenb. In a way in sagenb that's stuff that is only use to build/run sagenb and serves no other purpose. In the case of R/rpy I think it could be thought of as backward. sage access R through rpy if I am not mistaken. So rpy is the real dependency of sage that is the only thing requiring R.
Francois -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
