yade-dev team mailing list archive
-
yade-dev team
-
Mailing list archive
-
Message #00165
Re: my impression of BZR
1, 2 and 5 come from the fact that bzr checkout is really slow (yes, I was
also disappointed to see that). I addressed that on launchpad's IRC and will
see with the admins next week. It affects only checkouts/pulls, it is not
caused by overloaded servers. One of them told me that it is a known problem
and is being worked on, without any further specification. Speed
optimizations are said to be priority for 1.0 release which should be this
year, so it will improve very likely.
If 5s for diff really disturb your workflow, get the full (heavyweight)
checkout and work on that one. You need to do that once per computer, so it
is not a big deal (yes, it takes 2h in this situation). For your convenience
and for convenience of others, you can download
http://geo.hmg.inpg.fr/~smilauer/yade/yade-bzr-snapshot-checkout.tar.bz2,
then run "bzr update" there and you have full up-to-date repository. There
is apparently to do that directly (bzr asking launchpad for tarball of the
branch through the webserve plugin) but that is yet to find out. Once you
have heavyweight checkout, "bzr diff" will work fast, since it will not need
to connect to launchpad.
I don't know what you want GUI for, but have you tried "bzr viz" and "bzr
g*" for that matter?
The advantage of decentralized vcs is that you can have your local branch,
commit to it and push it upstream once some logical part of the work is
done. It probably has zero advantage for you, since you are the central
developer, but I do appreciate that a lot and other people will as well. I
have yet to find out how branches and checkouts are different (except that
the former are pulled/pushed and the latter checked out/commited).
V.
_______________________________________________
yade-dev mailing list
yade-dev@xxxxxxxxxxxxxxxx
https://lists.berlios.de/mailman/listinfo/yade-dev
Follow ups
References