Minh Nguyen wrote:
> Hi Jaap,
> 

Hi Minh,

> On Tue, Jul 14, 2009 at 7:33 AM, Jaap Spies<j.sp...@hccnet.nl> wrote:
> 
> <SNIP>
> 
>>> So it is save to do upgrade #81 to my systemwide sage install starting
>>> with sage-1.5.1,2? Latest install is sage-4.0.2.
>>>
>> Replying to myself: I gambled and:
>>
>>
>> [j...@paix ~]$ sage
>> ----------------------------------------------------------------------
>> | Sage Version 4.1, Release Date: 2009-07-09                         |
>> | Type notebook() for the GUI, and license() for information.        |
>> ----------------------------------------------------------------------
>>
>> sage:
>>
>>
>> Congrats to sage -upgrade!
>>
>> One thing I noticed is the building of the documentation: twice or trice?
> 
> I may misunderstand your question, but here goes... When upgrading to
> Sage 4.1 or compiling it from source, the (HTML version of the)
> documentation is built in the process -- only the reference manual is
> built during that time. But having successfully upgraded/compiled, one
> can still do
> 
> ../sage -docbuild reference html
> 
> in SAGE_ROOT and the reference manual, in this case, still gets built
> a second time.

This is not much of a question. I'm really happy to have my system wide
install upgrades for the 81-th time!

  Argh! It takes long enough the first time round, but
> another time? :-(  

I saw this happen. And moreover I see this happen every time I do
an upgrade and after that doing a 'make test' starts a new build
of the documentation!
I think the documentation build system needs some polishing.

Jaap



--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to 
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to