Improving init workflow [was: Re: [RFC] branch --bind]

[A. S. Budden]

2010/1/5 Tim Michelsen <timmichelsen at gmx-topmail.de>:
> I like this optimasation initative.
>
> I work with a central server / repository workflow.
> In order to create a new project I currently run:
>
> 1) bzr init sftp://my.remote.server.net/newproject
> 2) bzr co sftp://my.remote.server.net/newproject
>
> It would be nice if both could be combined.
>
> Also, when using the Eclipse IDE, it comes more complicated:
>
> 1) create a new Pydev project "newproject" in Eclipse
>    (This creates the .project and other Eclipse files)
> 2) close Eclipse
> 3) cp newproject newproject_ecl
> 4) bzr init sftp://my.remote.server.net/
> 5) bzr co sftp://my.remote.server.net/newproject
> 6) cp -r newproject_ecl/* newproject
>   (copy the Eclipse configurations in the checked out working branch)
> 7) rm-rf newproject_ecl
>
> I would appreciate any hints on how to accelerate this procedure.

The way I would do this (although I've not tried over sftp) is to use
my patched version of the Bazaar Explorer GUI [1].  Go to the
initialise dialog (in the "start a new project" section) and select
"Remote feature branches".  Enter the remote location into "Location".
 Enter the location for the working copy in "Work Location".  Click
OK.

This will create the remote repository and check it out (exactly as
per your commands) locally.  I'd then start Eclipse.  Create a new
Pydev project in the location that set as the "Work Location".  Then
you're done.

Hope that helps; feel free to add any comments or suggestions for
improvements on the patch at [2].

Al

[1] lp:~abudden/bzr-explorer/remote-feature-branches
[2] https://code.launchpad.net/~abudden/bzr-explorer/remote-feature-branches/+merge/15487

-- 
http://sites.google.com/site/abudden