Hi Charles, > This might be one benefit to subversion. It might be (I don't know, I've not used subversion so far). But the problem I see for buildtool is not so much that it's too hard to fetch a file for a specific branch, but rather that buildtool currently isn't fetching anything other than HEAD. So, one would have to make pretty much the same changes to buildtool, wether we're using subversion or not. Wether the url created is <base-URL>/tags/something/filename (for subversion) or <base-URL>filename?rev=HEAD&only_with_tag=something (for viewcvs) seems to be an implementation detail to me. Actually, that could be something to try: * add a branch in CVS for each release * append "&only_with_tag=something" to each URL to fetch from viewcvs (based on wether the user supplied a branch tag or not). Of course, this would only work if the initial checkout of buildtool was done for the right branch too.
This _could_ work (basically, it's along the lines of what Erich suggested). > ...also, since branches and tags are "free" (zero-copy) in subversion, > they don't suffer from the performance penalties encountered with CVS, > meaning it's faster/easier to create them as well as easier to use them, > so they're more likely to be properly taken advantage of. Add to that the fact that the subversion servers might work reliably more often than the CVS servers. The reason I'm not spending my evenings trying to port everything to subversion is not because I think CVS is superior to subversion (I know it fixes some of the issues CVS has) - it's simply that the benefits we might get don't outweigh the amount of time that would be needed to do the port (to me, I'm not speaking for anybody but myself - somebody else might have other priorities, and possibly also more spare time, and might even get a kick out of switching one source control system with another. To me, a source control system is simply a tool to do a job, and unless it causes more pain that it's worth, I'm unlikely to change it, unless I am _extremely_ bored). Martin _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
