[GSoC] Development repository

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

[GSoC] Development repository

siko1056
Hi Eduardo,

Regarding your development repository you should maintain an own copy of the official Octave repository. For example last year Jordi was nice to provide us a repository [1]. But as we have discussed in IRC you can also use another public service with free plans like Google-Code or Bitbucket. For the latter one you should repeat the following steps in order to setup your repository:

1. Create a new _public_ repository at Bitbucket, e.g. "myoctave", assumed account there is "myLogin"
2. Clone the official Octave repository to somewhere on your filesystem.


3. Rename the "octave" folder to "myoctave" (maybe unnecessary, just to avoid confusion)
4. Edit "myoctave/.hg/hgrc"


5. Edit "myoctave/.hgsub"


This should do all the trick. Now push to your development repository

hg push gsoc-dev

Now you can start your project. Another must reads are [2] and [3]. This will make it easier for others to follow your development process. Please can you give me feedback about the success of this procedure? If so I will extend [2] about this way of creating a development repository.

Best,
Kai

Reply | Threaded
Open this post in threaded view
|

Re: [GSoC] Development repository

Eduardo
Hi Kai,

Thanks for the info. I do followed all the steps you mentioned but when I reach the push step happens that things start to upload but in the end that is what occurs:

pushing to https://edu159@.../edu159/octave-subrepo
pushing subrepo gnulib-hg to https://edu159@.../edu159/octave-subrepo/gnulib-hg
searching for changes
http authorization required                                                    
realm: Bitbucket.org HTTP                                                      
user: edu159                                                                   
password:
sending [ <=>                                                 ] 45232/45168 -1s
interrupted!                                             

I have to interrupt the process because it hangs. As you can see seems that more bytes are upload than expected! (45232/45168). Did you encounter similar problems while testing this option? Any ideas?

Eduardo


2014-04-28 14:32 GMT+02:00 Kai Torben Ohlhus <[hidden email]>:
Hi Eduardo,

Regarding your development repository you should maintain an own copy of the official Octave repository. For example last year Jordi was nice to provide us a repository [1]. But as we have discussed in IRC you can also use another public service with free plans like Google-Code or Bitbucket. For the latter one you should repeat the following steps in order to setup your repository:

1. Create a new _public_ repository at Bitbucket, e.g. "myoctave", assumed account there is "myLogin"
2. Clone the official Octave repository to somewhere on your filesystem.


3. Rename the "octave" folder to "myoctave" (maybe unnecessary, just to avoid confusion)
4. Edit "myoctave/.hg/hgrc"


5. Edit "myoctave/.hgsub"


This should do all the trick. Now push to your development repository

hg push gsoc-dev

Now you can start your project. Another must reads are [2] and [3]. This will make it easier for others to follow your development process. Please can you give me feedback about the success of this procedure? If so I will extend [2] about this way of creating a development repository.

Best,
Kai


Reply | Threaded
Open this post in threaded view
|

Re: [GSoC] Development repository

Jordi Gutiérrez Hermoso-2
In reply to this post by siko1056
On Mon, 2014-04-28 at 14:32 +0200, Kai Torben Ohlhus wrote:

> Regarding your development repository you should maintain an own
> copy of the official Octave repository. For example last year Jordi
> was nice to provide us a repository [1].
[snip]
> 5. Edit "myoctave/.hgsub"
>
> gnulib-hg = http://www.octave.org/hg/octave/gnulib-hg

If you're patient enough for me to setup a repo for you (I think this
year I'll do them at hg.octave.org/gsoc), there is no need to add
gnulib-hg paths.

- Jordi G. H.