-=| Luca Falavigna, 14.11.2012 21:24:00 +0100 |=- > kgb does not permit to output repo-id value in the string sent to > the IRC server, at least for SVN repositories (I haven't checked for > other kind of repositories). > > This is particularly useful to differentiate between multiple SVN repositories > when displayed in the same IRC channel,
I think the place to put the project ID is the "module" concept. This is normally mapped to the package name. I think prepending it with project ID will satisfy the request. There's an easy workaround for Git repositories, repository === package === module. In these situations one adds "--module $prefix/$module" to the client invocation ($module is the base name of $GIT_DIR with stripped extension). Subversion is not so easy. In the python-modules/python-apps case, these are separate repositories, which means separate hooks, which would allow separate $prefix. The problem is that the module can only be determined at execution time, applying regular expressions over changed paths. --module $prefix would void run-time detection. So my proposal is to add a client configuration option, which would prefix detected module with a custom prefix. I am not sure if I want to hardcode the prefix to be the same as the project name ('python-apps') or to allow a custom one ('apps'). I think I'd prefer the more flexible solution -- a --module-prefix 'string' option, instead of a --prefix-module-with-project option. What do others think? What would be the preference from user point of view? Ah, there's another detail. Putting everything on client side is nice, but then we lose the possibility to use different color when displaying the project prefix. Should we care about coloring?
signature.asc
Description: Digital signature