OK, I found out what to do: The new spkg is at http://www.warwick.ac.uk/staff/J.E.Cremona/cremona-20071219.spkg and linked from the trac page.
I would be grateful if someone could test this. John On 19/12/2007, John Cremona <[EMAIL PROTECTED]> wrote: > Thanks. Just one more question: how does one make a spkg? > > John > > On 19/12/2007, mabshoff > <[EMAIL PROTECTED]> wrote: > > > > On Dec 19, 1:43 pm, "John Cremona" <[EMAIL PROTECTED]> wrote: > > > Michael, > > > > Hi John, > > > > > Here's a better solution. Tell me if this is closer to what I should be > > > doing. > > > > > > I copied and unpacked cremona-20071124.p4 from my 2.9 fresh build to a > > > separate location. From in there I did (after "hg incoming") and "hg > > > pull" from some version of my own source tree which had the changes I > > > had committed in it. There was one small conflict (in the top level > > > Makefile) which I fixed. So now I have a copy of cremona-20071124.p4 > > > which does have all the changes (bug fixes etc) which I want to be in > > > the next Sage distribution. > > > > Excellent. > > > > > Now the question is: how to get this version to you. I see from "hg > > > log" that there (starting from the head) lots of changesets made by > > > me, going back to this one: > > > > > > changeset: 40:6c7dd2a4c889 > > > user: [EMAIL PROTECTED] > > > date: Wed Dec 05 19:34:53 2007 +0100 > > > summary: gcc 4.3 build fixes > > > > > > So if I make a bundle from that as base, you should be able to handle > > > it ok, right? > > > > Yes. Just put that spkg up somewhere to download and add a link from > > the related ticket. Also add "[with spkg]" to the summary. To do that > > change look toward the bottom of the trac ticket page and edit the > > "Summary" field. It is customary to increment the patch level, the > > date of the spkg or the version number pf the pskg [that is needed for > > updates to work] and also update SPKG.txt with some sort of log entry > > and commit that. I would suggest you use cremona-20071219.spkg since > > the new spkg has new functionality and is more than "mere" bug fixes. > > > > > If this works, I know what to do in future: I make sure that my > > > changes apply OK to the current Sage version of the code, managing any > > > conflicts which arise myself, and then submit the appropriate bundle > > > from there, instead of making the bundles in my won tree. > > > > Excellent. It is easiest for us to send you patches, which you > > evaluate and merge. Then you can send us an updated spkg which we will > > compile test and so on. > > > > > I guess the next step (in my education) is to use some kind of "sage > > > -clone" to make a copy of the cremona*spkg source (if that works). > > > > > > John > > > > Cheers, > > > > Michael > > > > > > > > > -- > John Cremona > -- John Cremona --~--~---------~--~----~------------~-------~--~----~ 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/ -~----------~----~----~----~------~----~------~--~---
