Deleting the old packages will also break optional packages on all old Sage versions, so there should be a sensible deprecation period before doing so.
IMHO the whole old-style package stuff should be removed at one point, which would greatly simplify the entire package management. We would need a better way to distribute stuff that is not part of Sage. E.g. point to a git repo with a spkg-install script that can then do whatever it wants. On Sunday, June 7, 2015 at 11:18:29 AM UTC+2, Jeroen Demeyer wrote: > > Hello, > > What's the current status on the old-style packages on the mirrors? Has > the move been completed? > > I am asking because there are still many obsolete old-style packages on > those servers. All packages which are > 1. superseded by a new-style package (like zeromq), or > 2. are currently in the main git repo (like extcode), or > 3. simply no longer used in Sage (like genus2reduction) > should be removed. > > This issue is currently blocking several Trac tickets (#18581, #18408 > and indirectly #18558). > > My main question is: how does one change the online package lists? > > Jeroen. > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
