Emile Snyder wrote:
I also wouldn't mind notes from people that have tried to migrate to
monotone but discovered they were unable to for some reason. What were
the deal breakers?
Some time ago we examined the possibility of integrating monotone to
gforge (we have a small testing installation in our school about to get
some school projects once it is ready) and there were several problems:
1) push performance
http://lists.gnu.org/archive/html/monotone-devel/2005-06/msg00096.html -
there was a patch to improve that but I haven't tried yet because
2) compilation time
http://lists.gnu.org/archive/html/monotone-devel/2005-06/msg00136.html -
this has improved mainly with gcc4.0 to the point that I am able to
compile from source but it is still a major pain in the ... because any
fixes I could try (or develop myself) take just to much time :(
3) one database per project
http://lists.gnu.org/archive/html/monotone-devel/2005-06/msg00090.html -
this seems to be possible now with the usher thing but I haven't tried
that either yet
4) long time for incoming revisions verification - this is supposed to
get better with the rosters code
5) dumb server support - server without monotone -
http://lists.gnu.org/archive/html/monotone-devel/2004-01/msg00040.html -
this seems to be possible with net.venge.monotone.dumb
http://lists.gnu.org/archive/html/monotone-devel/2005-09/msg00220.html;
it is not there yet but it is a start :)
As you can see, all of my 'deal breakers' are being addressed so I see a
brighter future now :-). However I do not have any project using
monotone as a primary SCM.
Zbynek
--
http://zw.matfyz.cz/ http://robotika.cz/
Faculty of Mathematics and Physics, Charles University, Prague, Czech Republic
_______________________________________________
Monotone-devel mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/monotone-devel
