It would be annoying to use anything other than its own repo due to the requirement for xretrace directory being directly under the config directory.
By having dedicated xretrace repo, I can git clone it right into my config directory and get xretrace subdirectory. Then if I have changes, I can edit them right there and the push back to git. Then when I was done in Linux and wanted to try it in windows, I easily cloned it under my windows config dir and got working very fast.
If I use a common repository, the xretrace files will not be under the config directory - cloning directly under there won't put them in the right directory. So I would clone somewhere else. Then I would have to copy the files over - which is error prone. Then if I make changes to the files, I have to make sure to copy them back to the git repo for pushing, this is also error prone.
This is why I prefer a dedicated repository for now.
If being a subdirectory of config dir was not a requirement, or if the combined repo could be cloned directly under the config directory and the xretrace macro files could be updated to take this into account, then it would be better. But I don't have the time to invest right now to change this, or to create a loader utility. Perhaps if someone took the time to do that then we could have a common repo, but I can't do it at the moment. So I would propose to make my private repo public and then when someone can invest in making it so that one can clone the combined repo directly under the config directory, or make xretrace usable outside the config directory, then can move it into a common repo.
xretrace works fine for me in Linux x64, CentOS under SlickEdit v24 with my changes. I had to make another minor change to get it to work, change all the #import "dlinklist.e" to #import 'DLinkList.e' as Linux file system is case sensitive.