Changes between Version 78 and Version 87 of Ticket #9433


Ignore:
Timestamp:
01/13/11 07:38:33 (10 years ago)
Author:
vbraun
Comment:

After some rediffing I built it successfully on top of Sage-4.6.1.rc1 (identical to the Sage-4.6.1 release) with the following updated files:

  • trac_9433-scripts.v5.patch -> trac_9433-scripts.v5.2.patch
  • install -> install.2
  • deps -> deps.2

I've changed the main ticket documentation accordingly.

For reference, here is a list of files in the root repository: 

[vbraun@volker-two sage-4.6.1.vb2]$ hg st --all | grep -v '^I'
C .hgignore
C .hgtags
C COPYING.txt
C Makefile
C README.txt
C ipython/ipy_profile_sh.py
C ipython/ipy_user_conf.py
C ipython/ipythonrc
C ipython/ipythonrc-math
C ipython/ipythonrc-numeric
C ipython/ipythonrc-physics
C ipython/ipythonrc-pysh
C ipython/ipythonrc-scipy
C ipython/ipythonrc-tutorial
C sage
C spkg/README.txt
C spkg/gen_html
C spkg/install
C spkg/pipestatus
C spkg/root-spkg-install
C spkg/standard/README.txt
C spkg/standard/deps
C spkg/standard/libdist_filelist
C spkg/standard/newest_version

Really, any kind of root repository would be better than the caveman technology we have in place right now. I read through all the scripts and they do make sense to me. I built my private release using sage -sdist <version> and it compiled fine. You guys put a lot of effort into this ticket to make sure that nothing breaks, and I think it really is the time to integrate this with Sage.

Positive review.

Jeroen, can you plug this into 4.6.2.alpha as soon as possible to give it as much exposure as possible?

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #9433

    • Property Status changed from needs_review to positive_review
    • Property Reviewers changed from Leif Leonhardy to Leif Leonhardy, Volker Braun
    • Property Milestone changed from sage-4.6.1 to sage-4.6.2

  • Ticket #9433 – Description

    v78 v87  
    1 Put the text files in $SAGE_ROOT, and also the text files in spkg, under revision control.  (See the discussion at the end of #9351.)
     1Put the text files in `$SAGE_ROOT`, and also the text files in spkg, under revision control.  (See the discussion at the end of #9351.)
    22
    33Here are the instructions:
    44
    5  - apply the patches trac_9433-sage-repo.2.patch and trac_9433-scripts.v5.patch
    6  - move the attached file "hgignore" to SAGE_ROOT/.hgignore (note that this is a ''new'' file)
    7  - move the attached file "root-spkg-install.v2" to SAGE_ROOT/spkg/root-spkg-install (note that this is a ''new'' file)
    8  - move the attached file "install" to SAGE_ROOT/spkg/install
    9  - move the attached file "deps" to SAGE_ROOT/spkg/standard/deps
     5 - apply the patches `trac_9433-sage-repo.2.patch` and `trac_9433-scripts.v5.2.patch`
     6 - move the attached file `hgignore` to `$SAGE_ROOT/.hgignore` (note that this is a ''new'' file)
     7 - move the attached file `root-spkg-install.v2` to `$SAGE_ROOT/spkg/root-spkg-install` (note that this is a ''new'' file)
     8 - move the attached file `install.2` to `$SAGE_ROOT/spkg/install`
     9 - move the attached file `deps.2` to `$SAGE_ROOT/spkg/standard/deps`
    1010
    11 Then '''from $SAGE_ROOT''', run the attached script "hg_script" to create the Mercurial repository.
     11Then '''from $SAGE_ROOT''', run the attached script `hg_script` to create the Mercurial repository.
    1212
    13 To test upgrading, try
    14 {{{
    15 ./sage -upgrade http://sage.math.washington.edu/home/palmieri/misc/9433/sage-4.6.1.9433.alpha0/
    16 }}}
    17 You can then try
    18 {{{
    19 ./sage -upgrade http://sage.math.washington.edu/home/palmieri/misc/9433/sage-4.6.1.9433.alpha1/
    20 }}}
    21 to test an upgrade which changes an existing root repo: it is supposed to upgrade without error, changing just the beginning of the file SAGE_ROOT/README.txt.