On Friday, May 3, 2013 3:14:30 AM UTC+8, Gary McConnell wrote: > > hi Basu > > really sorry about this - I've just gotten around to trying this again - > but I am afraid I simply don't understand the most basic things of what I > have to do. You are right that indeed the patch file thingo seems to have > been created. So I went in search of these mysterious files and tried to > unpack the 5.8 stuff, but all it does is try to install it, which crashes > (please see attached screenshot) ... and obviously if I try to open the > .spkg thing itself inside an editor I just get utter gibberish ... >
Oh. I never asked you to *install* it. I asked you to simply *unpack* it. Run the following command from outside your sage installation directory. tar xvf /path/to/sage-5.8.spkg Then you will see a sage-5.8 directory in the directory you are in. > > Also it has been over 20 years since I last used vi or emacs ... is there > a window-based OS X text editor for morons like me please? eg Can I just > use TextEdit? :) > > I hope I'm not depressing you with this as much as I am myself .... > > Thanks again for all your kind help > > Gary > > > On Sat, Apr 27, 2013 at 4:10 AM, P Purkayastha <ppu...@gmail.com<javascript:> > > wrote: > >> On 04/26/2013 09:05 PM, Gary McConnell wrote: >> >>> Hi >>> >>> OK I have successfully raised trac tkt 14493, but that's about it. I'm >>> afraid I am so unused to this stuff that I cannot even follow the >>> instructions above. I tried to download 5.8 from that link, but it >>> failed to install. But I'm not even sure I was meant to install it! ie >>> maybe I just need the code stored somewhere - not sure what you meant >>> ... (I already have 5.7 working in this machine). I set up the file from >>> step 2, and then from step 4 I changed directory to Applications/sage >>> but Applications/sage/sage is a file not a directory. So I ran "./sage >>> -hg qnew 14493_documentation.patch" and it quietly blinked for a second >>> and then gave me a new command line - apparently doing absolutely >>> nothing! So when you say hack hack hack etc :) I am not sure what I am >>> supposed to be hacking!! >>> >>> Sorry if this is moronic, but I'll get there eventually .... >>> >> >> Hello, >> No, I outlined the instructions below if you don't want to install the >> sage source. After the step 4 ii) you will get no output. But you can check >> that the patch file has been created by using the command >> >> /path/to/sage -hg qser >> >> Note that I wrote /path/to/sage because it is supposed to be the sage >> script from your existing sage installation, NOT the unpacked sage-5.8 >> directory. >> >> By "hack hack", I meant that you just carry on with the changes you want >> to perform on the actual files. The hg will keep track of the changes. You >> can see a diff of the changes when you run the command >> >> /path/to/sage -hg qdiff >> >> Hope that helps, >> basu. >> >> >>> If you don't want to install the sage from source, you can download >>> the sage spkg and work with that. This is OK since you intend to do >>> only documentation changes. In this case, follow the steps below: >>> >>> 1. download the sage spkg from >>> http://www.sagemath.org/__packages/standard/sage-5.8.__spkg >>> >>> <http://www.sagemath.org/packages/standard/sage-5.8.spkg> >>> This contains the source code. >>> >>> 2. Create a file in $HOME/.hgrc containing your name as mentioned >>> here: >>> http://www.sagemath.org/doc/__developer/producing_patches.__html >>> >>> <http://www.sagemath.org/doc/developer/producing_patches.html> >>> >>> 3. Open a ticket in trac so that you can get the ticket number. >>> Let's say the number is 12345. >>> >>> 4. Use the inbuilt mercurial inside Sage to create the patch. >>> i) First change directory to the unpacked sage/sage directory >>> ii) Next, run the command (where /path/to/sage is where the sage >>> script is present and 12345 is the ticket number) >>> /path/to/sage -hg qnew 12345_documentation.patch >>> iii) Hack hack hack and make your changes :) >>> You will need to follow the developer documentation for syntax and >>> formatting. >>> iv) Now that you are satisfied with your changes, run >>> /path/to/sage -hg qref -m "a one line description of your changes" >>> v) Make hg generate the patch: >>> /path/to/sage -hg export qtip > ~/$(/path/to/sage -hg qtop) >>> >>> 5. Go back to the ticket and upload the patch that is present at >>> ~/12345_documentation.patch >>> >>> Hopefully, this procedure will become much simpler after the move to >>> git, since trivial changes can be made directly in github (if the >>> project remains hosted in github). >>> >>> >>> -- >>> You received this message because you are subscribed to a topic in >>> the Google Groups "sage-support" group. >>> To unsubscribe from this topic, visit >>> >>> https://groups.google.com/d/__topic/sage-support/__3mekDq5Stvk/unsubscribe?hl=en >>> < >>> https://groups.google.com/d/topic/sage-support/3mekDq5Stvk/unsubscribe?hl=en >>> >. >>> >>> To unsubscribe from this group and all its topics, send an email to >>> sage-support+unsubscribe@__googlegroups.com >>> <mailto:sage-support%2bunsubscr...@googlegroups.com <javascript:>>. >>> >>> To post to this group, send email to >>> sage-s...@googlegroups.com<javascript:> >>> <mailto:sage-s...@googlegroups.com <javascript:>>. >>> Visit this group at >>> http://groups.google.com/__group/sage-support?hl=en >>> <http://groups.google.com/group/sage-support?hl=en>. >>> For more options, visit https://groups.google.com/__groups/opt_out >>> <https://groups.google.com/groups/opt_out>. >>> >>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "sage-support" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> >>> an email to sage-support...@googlegroups.com <javascript:>. >>> To post to this group, send email to sage-s...@googlegroups.com<javascript:> >>> . >>> Visit this group at http://groups.google.com/group/sage-support?hl=en. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> >>> >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "sage-support" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/sage-support/3mekDq5Stvk/unsubscribe?hl=en >> . >> To unsubscribe from this group and all its topics, send an email to >> sage-support...@googlegroups.com <javascript:>. >> To post to this group, send email to sage-s...@googlegroups.com<javascript:> >> . >> Visit this group at http://groups.google.com/group/sage-support?hl=en. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at http://groups.google.com/group/sage-support?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
