What version of sage are you running? If it was 4.3.5 then you could do the following. Start in the directory where sage is installed (usually called SAGE_ROOT). I assume that this sage is in your path.
sage -clone ratfunc ## wait a while cd devel/sage-ratfunc sage -hg qinit sage -hg qimport http://trac.sagemath.org/sage_trac/raw-attachment/ticket/4000/trac4000_433_combined.patch sage -hg qpush sage -b and now when you start sage you'll have the patched version running. (When I did this with version 4.4 it was the qpush stage which failed since the patch would not merge cleanly onto that version). when you have finished you can just do sage -b main and you'll be back to te main, unpatched, branch. John On 30 April 2010 15:25, Pierre <pierre.guil...@gmail.com> wrote: > >> Would it be an option for you to apply the patch at >> >> http://trac.sagemath.org/sage_trac/ticket/4000 > > well, i went to sage-days in marseille and i'm supposed to know about > these things... but mostly i went home feeling that it was just a bit > too complicated... i barely remember that step 1 is "sage -b > new_branch_name". If you care to take me through the rest of the > procedure i might give it a try (would I need the latest sage as > well ?), but don't bother unless you have nothing better to do... > > -- > 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 > -- 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
