Simon King wrote: > Hi Leif, > > On 2016-08-28, leif <not.rea...@online.de> wrote: >> I have to admit I had to try whether this has changed "recently", but >> no, already installed optional / experimental packages still aren't >> reconsidered upon upgrading Sage, i.e., you currently have to explicitly >> "reinstall" them if there's a new version available. > > Seriously?? I thought that automatic upgrade of packages is one of the > reasons why one was supposed to do "make" after "git pull". Is there > consensus that installed packages *should* automatically be upgraded > to the latest available version, in order to avoid known breakages?
It was always true for *standard* packages. But in my test I indeed made a mistake, and meanwhile also optional and experimental packages get reinstalled (hence upgraded) in case they had been installed previously. (They do get reinstalled *after* docbuilding, so I actually missed that, not wanting to wait, since docbuilding takes ages even if nothing changed / really happens.) Sorry for the noise. -leif -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
