Hi, it could be nice to have a list of the non-migrated spkgs that are still needed. Depending on its size, working on a raw migration to get rid of the old-style spkgs will be a great simplification.
As for me, i see: - cbc - nauty A side effect would be to easily fix the currently broken "sage -optional" and "sage -standard" commands, they currently lists old version found on the web while with a complete move to the new-style packaging it will suffice to look at the local build/pkgs directory. Ciao, Thierry On Tue, Jan 06, 2015 at 01:18:32PM +0530, Nathann Cohen wrote: > Yo ! > > > Reason: There still exist old style spkgs (I am to blame for one > > optional old style spkg), and as long as that is the case, information > > on their format is relevant. > > I was wondering about that, actually. If they are ever updated again, > shouldn't they be converted to new style spkg ? > > It is a bit like the recent removal of the "sagedev" scripts > documentation. While we keep the feature, I thought that we should > stop advertising it. > > This being said, I hear and understand your objection: I asked the > question in order to know what you thought of it, and if you do not > like the idea the problem is settled :-) > > Have fun ! > > Nathann > > -- > 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. > > -- 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.
