William Stein wrote: > On Sat, Nov 14, 2009 at 11:40 AM, Dr. David Kirkby > <david.kir...@onetel.net> wrote: >> William Stein wrote: >>> Hi, >>> >>> I want to formulate a rough ideal strategy for how to deal with >>> "optional stuff" in Sage, and get feedback. >>> PROPOSAL: 1. Before releasing a new version of Sage, we test >>> installing all of the optional spkg's on the most recent 64-bit >>> version of Ubuntu. If any package fails, the spkg maintainer is >>> notified, and if they don't fix the issue within one week, the spkg is >>> moved to "experimental" = (still available via "sage -i" but we make >>> no guarantee it will work in any way). If there is no spkg >>> maintainer or the maintainer is not responsive, we try to get a new >>> maintainer, and if none materialize the spkg is moved to experimental. >> >> The idea sounds good, but would it not be better to have another option to >> download 'experimental' packages? > > I don't understand this question. > > William
I assume 'experimental' are less stable than 'optional'. IMHO, the user downloading the file should be made aware it is experimental, and so one way to do that would be to have an option like sage --install-experimental some_possibly_broken_package Dave --~--~---------~--~----~------------~-------~--~----~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
