I was a bit surprised to find that echangelog took quite a while when I tried to add a message to the svn-based java-experimental overlay. pstree and ps told me it was a "bzr root" command running somewhere in the background. I assume that because I've got dev-util/bzr-svn installed, bzr thought it might be responsible for svn repositories as well, so it went on and tried to create a revision cache of all the revisions in the subversion repository. Which of course takes time. I suggest you check for svn first, and bzr only later on, to avoid such issues.
It just picks bzr if there is a .bzr directory. So if you have a svn repository and also a bzr repository inside of it it will choose bzr.
Hm, ignore my previous comment.. I'll take a look at it.
Created attachment 217868 [details, diff] echangelog-check_vcs_dir.diff Please try my patch, it adds support for exactly what I said in my first comment. That might help in this case.
So please try http://sources.gentoo.org/viewcvs.py/gentoolkit/trunk/gentoolkit-dev/src/echangelog/echangelog?r1=688&r2=736
Sorry for the delay... (In reply to comment #4) > So please try > http://sources.gentoo.org/.../echangelog?r1=688&r2=736 Works like a charm, and looks good as well. One minor point, though: you might wish to write "sort(keys(%vcs))" instead of "keys(%vcs)" so you can ensure a consistent order in which vcs are checked. Nested vcs call for trouble in this setup, but that way you'd at least get reproducible trouble. Will you mark this fixed once the new code got released?
Oh, and you might wish to introduce a command line switch so users can override the repository autodetection.
(In reply to comment #5) > Sorry for the delay... > > (In reply to comment #4) > > So please try > > http://sources.gentoo.org/.../echangelog?r1=688&r2=736 > > Works like a charm, and looks good as well. > > One minor point, though: you might wish to write "sort(keys(%vcs))" instead of > "keys(%vcs)" so you can ensure a consistent order in which vcs are checked. > Nested vcs call for trouble in this setup, but that way you'd at least get > reproducible trouble. Done. > > Will you mark this fixed once the new code got released? > Yep. (In reply to comment #6) > Oh, and you might wish to introduce a command line switch so users can override > the repository autodetection. Done :)
Fixed in 0.2.6.13-r1.
