On Sun, 16 Jan 2005 10:32:20 -0700, Clinton Begin wrote: > Cool. I have the tarball from SourceForge. I was planning on > converting the repository from CVS to SVN and rearrange it as > described. Can our ops guys merge two SVN repositories? Or is > that a nightmare? Is it easier if I just leave it as CVS?
I asked on the infrastructure list about merging and joining, and which way would be the best to go, but didn't get a response. I had thought we could just give them both tarballs and let whoever does it do the best they can. Once it was up, we could refactor it there. But, if we'd like to submit a more finished product to the ASF, we could ask WUSH.NET if they could convert the CVS and merge it our existing SVN repository. They did this for me with the Struts CVS, when we were deciding whether to go with SVN or not. The response time has always been good, generally over night. Or, if you want to convert and refactor it yourself, we could get the SVN dump of that, and see if WUSH.NET can merge it into ours. We could then get the dump of the combined WUSH.NET SVN and hand that to the infrastructure guys. > Also, with regard to the 3rd party (non-ASF) DLLs (Hibernate etc.), > are you physically deleting them from the repository (can you do > that with SVN)? I was going to delete the ,v file from cvs > entirely, so that the 3rd party jar files aren't even in history. It's not easy to remove any artifact from SVN. You can do it, but it's messy. But if we are transferring a dump, I believe we might be able to excise the folder in transit. (Beam me up, Scotty ... and can you remove the mole while you are at it?) The key point is whether the ASF is distributing a *GPL binary with it's own distribution. We haven't had an ASF distribution yet, so we are clear on that point. > > Cheers, > Clinton -Ted.
