That's almost default behaviour: bzr branch http://bazaar.launchpad.net/%7Emdipierro/web2py/devel
now, work your things, commit, update, etc, and when you want to sync to newest web2py, just bzr pull if it fails (diverged branches), do bzr merge http://bazaar.launchpad.net/%7Emdipierro/web2py/devel and you're good to go with the newest web2py while keeping your own local repo. On Apr 8, 10:21 am, Timmie <timmichel...@gmx-topmail.de> wrote: > Hello, > I need some advice on using the development version that I checked out > from Launchpad. > > My own applications would be developed in a subdirectory web2py/ > applications. > Off cource, I do not want them to be pushed / commited to the main > web2py repository. > > How do you work with the latest development version whilist versioning > your own applications to a (central) different repository? > > Maybe I am overlooking something here, but advice would help me here > getting set up properly with the framework. > > Thanks in advance, > Timmie --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
