#18820: Upgrade R to 3.2.1
-------------------------------------+-------------------------------------
       Reporter:  charpent           |        Owner:
           Type:  enhancement        |       Status:  needs_review
       Priority:  major              |    Milestone:  sage-6.8
      Component:  packages:          |   Resolution:
  standard                           |    Merged in:
       Keywords:  r-project          |    Reviewers:
        Authors:  Emmanuel           |  Work issues:
  Charpentier                        |       Commit:
Report Upstream:  N/A                |  9a9c4ccd78dda128da41df76089fb87462a870a4
         Branch:                     |     Stopgaps:
  u/charpent/upgrade_r_to_3_2_1      |
   Dependencies:                     |
-------------------------------------+-------------------------------------

Comment (by charpent):

 Replying to [comment:7 ncohen]:
 > Hellooooooo,
 >
 > > You advised (see #16711 about upgrade to 3.1.1) adding this file to
 document the renaming of the tarball (from R-x-y-z.tar.gz to
 r-x-y-z.tar.gz), needed by the then-current convention of all-lowercase
 tarball names.
 >
 > A `spkg-src` file to document a renaming? Why? `O_o`
 >
 > > Do you advise keeping a no-op {{{spkg-src}}} ?
 >
 > No. I advise to keep a file that re-builds the archive from network
 ressources only.

 Please don't do that (unless you have a solid reason to do so) : some
 firewall setup do exceedingly annoying thing to network downloads. The
 recent "enhancement" to downloads that tries to select the closest/fastest
 mirror left me with an unupdateable tree (and, yes, this machines lives
 behind a "corporate-style" fascist firewall, run by incompetents...). I
 didn't yet had time to figure out how to unwedge it in order to test your
 (and vbraun's) solution)....

 > Then it becomes easier to check that the archive's content is what it
 should be. I do not see anything wrong with a script that downloads a
 distant file (whose url is generated from the locally stored version
 number), and does nothing else to it if there is nothing else to do.
 >
 > Actually, I will try to solve this once and for all. I'll write some
 'sage --sanity-check-package whatever' that uses whatever's spkg-src
 script (if any), and checks whether the content of the file in `upstream/`
 matches it.
 >
 > This way, checking that the archive is legit will only be a call to
 'sanity-check'. In this setting, your spkg-src, even though it just
 downloads something, will be useful.

 Again, ponder what you're planning. Im currently in a hell paved of yur
 good intentins.

 Whatever you decide to do, could you please open a SEPARATE ticket,
 instead of hijacking this innocent R upgrade YET AGAIN (that would be the
 fourth time...) ? Thanks in advance !

--
Ticket URL: <http://trac.sagemath.org/ticket/18820#comment:8>
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 http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.

Reply via email to