Hi Max, On Mon, 2008-03-03 at 14:52 -0800, Max Kanat-Alexander wrote: > I'd suggest that you switch to it entirely. I'd be happy to add > any features that you need that it doesn't have, as long as they're > within the scope of the project. And any performance enhancements > needed, I'd be happy to give you those, too.
Does VCI support operations when running from inside a hook of the SCM system ? e.g. while executing pre-commit in Subversion, run gather metadata about the on-going transaction (e.g. by running the svnlook utility). > Hm, what would a repository configuration file be? VCI wouldn't > need all that much configuration, since it's all object-oriented--you > just connect to a Repository, ask for a Project, and then call some Indeed. VCI only needs a "repository URL" so to speak. > methods on it. I'm guessing that a configuration file would be more > something that SCMBug would use and then pass data to VCI. For example, CVS stores its hooks within the repository in CVSROOT. Scmbug in return, saves its glue configuration file inside the repository, inside CVSROOT/etc/scmbug/glue.conf. When a hook executes, the Scmbug glue reads this file to determine how to act, which policies to implement, etc. This all works great, but when its time to build additional utilities that need to consult the glue.conf file, then these utilities now need to checkout the repository first to get that file. Still, that works for CVS. But not for Subversion, which does not support this notion of repository configuration files that live inside the repository (instead, they live in svnrep/hooks). If these "utilities" need this configuration file, the utilities must be run from the machine that hosts the repository (this is a big limitation). So, would it possible for VCI to support this notion of being given a repository URL and the name of a configuration file that lives inside the repository, and have VCI provide that file ? e.g. maintain a "/trunk/3rd_party_configuration/<conf_files_here>". Or is this an abstraction that only Scmbug needs, and should be implemented on top of VCI ? I'm having trouble accepting that only Scmbug would need this feature. TortoiseSVN for example requested this from the Subversion team, but they did not implement it yet. If we are to switch to VCI (and we SHOULD), and access to "configuration files" is needed and should be implemented somewhere, should it be implemented by VCI ?
signature.asc
Description: This is a digitally signed message part
_______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
