On Dec 1, 9:36 pm, John H Palmieri <[EMAIL PROTECTED]> wrote: Hi John,
> Some random questions about the optional packages available for Sage: > > Which is more up-to-date: the list obtained by 'sage --optional', or > the list on the wiki <http://wiki.sagemath.org/ > optional_packages_available_for_SAGE>? (I'm guessing the former.) Yes, the former is more current. I think we should delete the page in the wiki since it is unmaintained. > Is the list obtained by 'sage --optional' the same as the list on > sagemath.org <http://sagemath.org/packages/optional/>? (I think so.) Yes, the html page is automatically generated when new spkgs are updated. > Should the optional packages boehm_gc-7.1.p0 and jmol-11.5.2-src-v2 be > deleted, because the first is now a standard package and for the > second, the (presumably newer) package jmol-11.6.rc8 is standard? Not all people will be running Sage >= 3.2.1. for a while, so I would keep the boehm_gc around for now. The jmol.spkg is special since the optional spkg is the source version. I guess it would be good if someone updated it one day. > I've also been trying to put together short descriptions of these, to > be put on various web pages and listed when you type 'sage -- > optional'. What's the procedure for implementing something like > this? Should I open a trac ticket, and if so, what file(s) do I > patch? (I can also post my list of descriptions here in sage-devel > for people to comment on.) There already is a ticket for that: #855 > It would also be nice to have descriptions for the standard packages > and the experimental ones, while we're at it... Yeah, SPKG.txt is supposed to do that. SPKG.txt is written in wiki text and is supposed to be copied into the wiki as they are updated. But many of them are incomplete and often the version in the wiki is not very current. Look at http://wiki.sagemath.org/Sage_Spkg_Tracking if somebody could just extract the current SPKG.txt files from the 3.2.1 release and update the good looking ones in the wiki and then start cleaning up the ugly ones it would be very nice. I mean to add one more section to the default SPKG.txt and that would be a list of all the spkgs that depend on this spkg. I.e. the SPKG.txt in numpy would list scipy as an spkg that depends on it. That way if one updates for example pari one would know that one would have to bump eclib and lcalc amongst others since it isn't always obvious what the dependencies are. Once we are done it would be nice to extract all the dependency data and create a graph for it :) > John Cheers, Michael --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
