I'm worried that this check is going to slow down a developer
working on a cloned copy. In this case, one is probably not interested
in updating. Could this auto-update be turned off by default in all clones?



William Stein wrote:
> On 5/18/07, David Joyner <[EMAIL PROTECTED]> wrote:
>> How would this work? If sagemath was down or there wasn't a net connection
>> would there be a weird error?
> 
> No.  It would try to contact sagemath once during each 1 week period.  If
> during that time it found that an upgrade is available, it would mark that 
> fact
> in a file.  That file would be printed on startup of SAGE from the command 
> line.
> 
> If contacting sagemath.org fails after 2 seconds, it would silently fail,
> and another attempt wouldn't be made for a week.
> 
> This will set off all kinds of firewall software in some
> environments... and rightfully so.
> 
>> Would it confuse users who could not update
>> (eg, students using the SAGE notebook in a lab)?
> 
> The message would be invisible to notebook users.  (??)
> 
> 
>>
>>
>> On 5/18/07, Nick Alexander <[EMAIL PROTECTED]> wrote:
>>> "William Stein" <[EMAIL PROTECTED]> writes:
>>>
>>>> Hi,
>>>>
>>>> This is a discussion of update/upgrade notification for SAGE for normal 
>>>> users.
>>>> Feel free to read it and share your thoughts.
>>>>
>>>> ---------- Forwarded message ----------
>>>>> Another suggestion I have, automatic notification of major new
>>>>> version releases:
>>>>>
>>>>> Say once a week, when  you start SAGE, it checks with the canonical
>>>>> SAGE server on the Net and if a significant version (like  2.5) has
>>>>> been released, it just says something like "A newer version of SAGE
>>>>> with software enhancements, version 2.5, is now available.  If you
>>>>> have administrative privileges for SAGE you may wish to install it
>>>>> with the command "sage -upgrade" from the command line.  Note that
>>>>> this may take some time, depending on the speed of your computer and
>>>>> network connection."
>>>> Maybe.  I'll running it by sage-devel.  One of the things I hate most
>>>> about software is stupid frickin' automatic notifications about upgrades...
>>>> They drive me crazy. Especially Adobe Acrobat's.
>>> One way to make notifications less obtrusive is to make them
>>> omnipresent.  That is, the banner could always read
>>>
>>> ----------------------------------------------------------------------
>>> | SAGE Version 2.5.alpha2, Release Date: 2007-05-02
>>> | Latest version is 2.5.alpha3, type upgrade() to upgrade.
>>> | Type notebook() for the GUI, and license() for information.        |
>>> ----------------------------------------------------------------------
>>>
>>> While we're at it, maybe the banner should also tell you if you're
>>> running a vanilla sage or a hacked sage and maybe what the last hg tag
>>> was.
>>>
>>> Nick
>>>
> 
> 


--~--~---------~--~----~------------~-------~--~----~
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://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~----------~----~----~----~------~----~------~--~---

Reply via email to