Changes between Version 20 and Version 22 of Ticket #9433


Ignore:
Timestamp:
08/11/10 19:31:26 (9 years ago)
Author:
jhpalmieri
Comment:

This seems to work for me, with one slight glitch: if I run "sage -upgrade" on a copy of sage which does not yet include the root repo, it lists the spkg's to be upgraded and asks me "do you really want to continue", then it does some stuff, and then it lists just the root_repo spkg and asks me again if I want to continue. The issue is that, before it has installed some of the upgraded packages, it doesn't know what to do with the root_repo spkg, so it doesn't get installed the first time through. I don't see any way around this, but it's a one-time problem.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #9433 – Description

    v20 v22  
    44
    55 - apply the patches trac_9433-sage-repo.patch and trac_9433-scripts.patch
    6 
    7 and create the Mercurial repository:
    8 
    96 - move the attached file "hgignore" to SAGE_ROOT/.hgignore
    107 - move the attached file "root-spkg-install" to SAGE_ROOT/spkg/root-spkg-install
    11  - cd $SAGE_ROOT
    12  - hg init .
    13  - hg add .hgignore COPYING.txt README.txt makefile sage sage-python
    14  - cd ipython
    15  - hg add *.py ipythonrc*
    16  - cd ../spkg
    17  - hg add README.txt gen_html install pipestatus root-spkg-install
    18  - cd standard
    19  - hg add README.txt deps libdist_filelist newest_version
    20  - hg commit
     8
     9Then '''from $SAGE_ROOT''', run the attached script "hg_script" to create the Mercurial repository.