[web2py] Managing routes.py with mercurial checkout

2010-08-09 Thread mwolfe02
I'm just looking for a best practice here. I am running web2py using a clone of the repository https://web2py.googlecode.com/hg/. This has worked really well for me. However, I just added a routes.py file. Clearly, I want to version control this file, but that requires committing the change to

Re: [web2py] Managing routes.py with mercurial checkout

2010-08-09 Thread Jonathan Lundell
On Aug 9, 2010, at 8:20 AM, mwolfe02 wrote: I'm just looking for a best practice here. I am running web2py using a clone of the repository https://web2py.googlecode.com/hg/. This has worked really well for me. However, I just added a routes.py file. Clearly, I want to version control this

Re: [web2py] Managing routes.py with mercurial checkout

2010-08-09 Thread Michael Wolfe
OK, but that still leaves a link to routes.py in the web2py repository. Do you use the Pull -- Update -- Merge -- Commit approach then when you update your web2py repository? On Mon, Aug 9, 2010 at 11:40 AM, Jonathan Lundell jlund...@pobox.com wrote: On Aug 9, 2010, at 8:20 AM, mwolfe02 wrote:

Re: [web2py] Managing routes.py with mercurial checkout

2010-08-09 Thread Jonathan Lundell
On Aug 9, 2010, at 9:06 AM, Michael Wolfe wrote: OK, but that still leaves a link to routes.py in the web2py repository. Do you use the Pull -- Update -- Merge -- Commit approach then when you update your web2py repository? Actually, I misdescribed my configuration slightly. I run my app

Re: [web2py] Managing routes.py with mercurial checkout

2010-08-09 Thread Michael Wolfe
Got it. I think that makes more sense than what I'm doing now. I probably outsmarted myself a bit trying to use mercurial to maintain the copy of web2py that I'm using to run my app (in my defense, when you've got a nice hammer (mercurial), everything looks like a nail). I thought about

Re: [web2py] Managing routes.py with mercurial checkout

2010-08-09 Thread Thadeus Burgess
As far as contributions go, you will just be sending diff files in. As long as your diff is clean it should not matter what is in your repository. Massimo does not use the hg import/export commands so you don't even need to commit any contributions to your local version anyways. -- Thadeus

Re: [web2py] Managing routes.py with mercurial checkout

2010-08-09 Thread Michael Wolfe
Thanks, Thadeus. I'd like to contribute at some point in the future and I wanted to make sure my design decisions wouldn't make that more difficult. I know you are a regular contributor, do you use a similar approach to what Jonathan uses? ie, do you run your apps using an 'install' of a web2py

Re: [web2py] Managing routes.py with mercurial checkout

2010-08-09 Thread Thadeus Burgess
Yes. I have one checkout that I always keep at the latest version. Its easy since I just clone the tagged revisions from mercurial. I simlink all of my applications to this single web2py instance. If I need to work on web2py, I clone a brand new repository from tip and then begin working. If I