[svk-devel] SVK SVN Mirroring Scenario

Stine, Matt Matt.Stine at STJUDE.ORG
Mon Jul 9 17:55:43 EDT 2007


We are getting ready to release a large body of code into open source,
and will be mirroring our local SVN repository to a repository located
at Google Code.  I have followed the online solutions available for
doing this with SVK, including the solution mentioned in the online SVK
book.  I do have a couple of tweaks that I need to do, and I want to
find out the best way to make this happen.

 

We have used some proprietary modules that we cannot distribute, and up
to this point have maintained them in our repository. I have since moved
them to another repository.  Since I know that an SVN delete only
removes from the HEAD revision, I want to find a way to make sure that
these are not mirrored to the external repository.  In my understanding,
an svk smerge without the -incremental option will accomplish this,
pushing only the HEAD revision out. Is that correct? Also, is there a
way to do this and maintain the history for the other files?

 

Also, some of these proprietary modules have been linked back in to the
project repository using svn:externals. I noticed that when I did the
smerge and then checked out from the now mirrored test repository, the
externals were brought in as well. I don't want this to happen. They
wouldn't be available to a user if they checked out from Google Code
because the said modules are in a repository behind our firewall, but I
also wouldn't want the users to experience any errors. Can this be done?
Is there a way to ignore the svn:externals property when mirroring?

 

Thanks.

 

Matt Stine

Senior Software Engineer

Hartwell Center for Bioinformatics and Biotechnology

St. Jude Children's Research Hospital

332 N. Lauderdale St.

Memphis, TN 38105

901.495.4602

901.495.2945 Fax

901.495.3578 #1314 Pgr

matt.stine at stjude.org

http://www.hartwellcenter.org

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.bestpractical.com/pipermail/svk-devel/attachments/20070709/d7099d58/attachment.htm


More information about the svk-devel mailing list