#20190: Upgrade R to 3.2.4
-------------------------------------+-------------------------------------
       Reporter:  charpent           |        Owner:
           Type:  enhancement        |       Status:  needs_work
       Priority:  major              |    Milestone:  sage-7.2
      Component:  packages:          |   Resolution:
  standard                           |    Merged in:
       Keywords:  r-project          |    Reviewers:
        Authors:  Emmanuel           |  Work issues:
  Charpentier                        |       Commit:
Report Upstream:  N/A                |  385c51d8fc95817eec10780fa40723d9f02865e0
         Branch:                     |     Stopgaps:
  u/charpent/upgrade_r_to_3_2_4      |
   Dependencies:                     |
-------------------------------------+-------------------------------------

Comment (by charpent):

 I'm wondering how to do this : upstream has adopted a curious name for
 this release ; furthermore, it has done it inconsistently :

 * the tarball is named {{{R-3.2.4-revised}}}, but
 * the source tree is named {{{R-revised}}}.

 Sage's build system chokes on this ; short of renaming the tarball and/or
 rebuilding it with a sensible source tree name, I don't see how to get
 Sage's building system accept this.

 We can either :

 * rename/rebuild this tarball consistently //via// spkg-src, or
 * skip this one-week wonder entierely (last time I looked, R 3.3.0 was
 scheduled in Apr 11, 2016).

 Your thoughts ?

--
Ticket URL: <http://trac.sagemath.org/ticket/20190#comment:18>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.

Reply via email to