The last releases of mr.developer (1.2 and 1.3) reduce the amount of surprises.
The packages from auto-checkout are now automatically added and removed from the list of development packages when you switch buildout configurations. Before you had to run develop reset and rerun buildout for that to work. If you have an existing checkout, you may want to reset it, so that this change is picked up.
The last used buildout configuration is now read directly. That means if you change source declarations in your buildout configuration, then you don’t have to rerun buildout anymore for mr.developer to pick up those changes. You still have to run buildout after changing the develop status of a package, but that’s the same as with a plain buildout without mr.developer.
Any chance we could get a:
bin/develop clean
…to remove the packages that are checked out but no longer in use? (ie. the ones marked with ~)
I know you can do this with a shell script and piping various things into each other, but it would be very convenient as a command.
Nice work!
Hi,
There appears to be a problem with 1.3 if you ran your buildout with a -t flag set before running bin/develop
I had a poke around in pdb and I’m fairly sure that it’s the -t flag that’s breaking it.
Not sure if this is the right place to report a bug, sorry if it’s not.
Tom
I can reproduce the issue, thanks. The right place for bug reports is http://github.com/fschulze/mr.developer/issues.
I know you can do this with a shell script and piping various things into each other, but it would be very convenient as a command.
+1
The “purge” command is in there for quite a while now. Only works for svn repositories though, as the other ones can’t be reliably checked to have everything on the server.