On 2014-04-25, Amit Jamadagni <[email protected]> wrote: > Hello William, > Thanks for the input. That was exactly what I was thinking. I > have cloned the git repo, I could not run ./sage directly without running > the make file. Where as in the lzma pack I could just extract and get on > with the development (after I did a pull). So am I missing something here > from the git repo as I could not run. I have cloned this repo > https://github.com/sagemath/sage. Thanks for all the help and input. no, you are not missing anything from the repo - but getting Sage from github (or trac.sagemath) will only give you the source code of everything, which you need to compile. After this is done (by doing make) you should have a working copy of Sage.
I suppose by 'the lzma pack' you mean the binary distribution of Sage for your platform. While you may use it for development, it is perhaps less suited for this - it is really meant for end users, not for developers, and various things there might be missing. HTH, Dima > > > On Fri, Apr 25, 2014 at 7:46 PM, William Stein <[email protected]> wrote: > >> On Fri, Apr 25, 2014 at 7:07 AM, Miguel Angel Marco >> <[email protected]> wrote: >> > To question 1, yes, you can. >> > To question 2, i don't see why you would want to do that. Why would you >> want >> > to push any binary to github? >> >> I'm guessing Amit is just confused and really means "can I push the >> source code that I got as part of the *binary* [...] to github". >> The answer is yes -- it's an unusual core design decision in Sage that >> even our "binaries" ship with the git repo, so users can immediately >> contribute back changes they make to a "binary". >> >> william >> >> > >> > >> > El viernes, 25 de abril de 2014 09:51:36 UTC+2, Amit Jamadagni escribió: >> >> >> >> Hello Miguel, >> >> >> >> Initially I used the following procedure to set the patch >> >> 1. Downloaded the lzma file and untarred it, >> >> 2. Then I did a git pull so I get the latest master >> >> 3. Then edit the necessary changes, then built it using ./sage -b and >> >> tested using ./sage -t, if everything was okay I used to commit onto the >> >> trac server. >> >> >> >> I had this doubt on setting the repo up.For a start I forked the repo on >> >> github and have cloned the sage repo from github onto my local system, >> I had >> >> to run the make file, here are my doubts on this subject: >> >> 1. Is running make once enough, in sense after once I have run make can >> I >> >> use ./sage -b after editing the code. >> >> 2. Can I push the binary that I have untarred from the lzma onto github, >> >> work on this code and then push intermediate tickets onto the trac >> server. >> >> >> >> It would be great if you could comment if I am going in the right >> >> direction. Thanks. >> >> >> >> >> >> On Wed, Apr 23, 2014 at 10:31 PM, Amit Jamadagni <[email protected]> >> >> wrote: >> >>> >> >>> Hello Harald, Miguel, >> >>> I would like to work on a repo and then create a >> >>> ticket on the trac server once there is sufficient amount of code in >> there. >> >>> I guess we can have few intermediate tickets with decent amount of >> code in >> >>> it rather than creating a single ticket with bulk code as it would be >> easy >> >>> to review. I have tried to setup the blog and here is the link >> >>> https://knotsknotted.wordpress.com/. >> >>> >> >>> >> >>> On Wed, Apr 23, 2014 at 9:27 PM, Harald Schilly <[email protected]> >> >>> wrote: >> >>>> >> >>>> Hello everyone, and yes, thank you for posting this. You almost read >> my >> >>>> mind ;-) >> >>>> >> >>>> On Tue, Apr 22, 2014 at 12:33 PM, Miguel Angel Marco >> >>>> <[email protected]> wrote: >> >>>> > Here are some tasks that you should do: >> >>>> > >> >>>> > 1) Create a blog ... >> >>>> >> >>>> Yes, everyone has to do this. Post a short or longer status update >> >>>> once a week ... and you can start right now with a nice introduction. >> >>>> What's also important is to "tag" the postings. For example, in >> >>>> blogger, wordpress and so on you can add a label like "sage" to your >> >>>> postings. Then, there is a view of your post where only those postings >> >>>> associated with that tag "sage" are visible. >> >>>> Why? I'll add this feed of postings to Sage's community blog: >> >>>> http://planet.sagemath.org ... where your postings will appear right >> >>>> next to all the other ones. So, once you have done this, please send >> >>>> me the blog url and an info about this tag. >> >>>> >> >>>> > >> >>>> > 2) Create a repository for your code on this project. Since sage >> uses >> >>>> > git >> >>>> > and guthub, i recommed you to use github. But if you prefear >> something >> >>>> > else, >> >>>> > like bitbucket, it is ok. >> >>>> >> >>>> Yes, Github or a branch on Sage's trac. In case you are working on the >> >>>> Android app, forking that project is of course the preferred way. >> >>>> >> >>>> Harald >> >>>> >> >>>> -- >> >>>> You received this message because you are subscribed to the Google >> >>>> Groups "sage-gsoc" group. >> >>>> To unsubscribe from this group and stop receiving emails from it, send >> >>>> an email to [email protected]. >> >>>> To post to this group, send email to [email protected]. >> >>>> >> >>>> Visit this group at http://groups.google.com/group/sage-gsoc. >> >>>> For more options, visit https://groups.google.com/d/optout. >> >>> >> >>> >> >> >> > -- >> > You received this message because you are subscribed to the Google Groups >> > "sage-gsoc" group. >> > To unsubscribe from this group and stop receiving emails from it, send an >> > email to [email protected]. >> > To post to this group, send email to [email protected]. >> > Visit this group at http://groups.google.com/group/sage-gsoc. >> > For more options, visit https://groups.google.com/d/optout. >> >> >> >> -- >> William Stein >> Professor of Mathematics >> University of Washington >> http://wstein.org >> >> -- >> You received this message because you are subscribed to the Google Groups >> "sage-gsoc" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at http://groups.google.com/group/sage-gsoc. >> For more options, visit https://groups.google.com/d/optout. >> > -- You received this message because you are subscribed to the Google Groups "sage-gsoc" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-gsoc. For more options, visit https://groups.google.com/d/optout.
