[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Multiple independent repositories

From: BRM <bm_witness_at_yahoo.com>
Date: 2005-01-31 18:22:07 CET

I noticed in the TortoiseSVN interface that there is a
"switch" repository command. What about using that? I
don't know what the command line equivalent would be,
but that should be able to let him do what he wants,
no? E.g. The following:

- Do work on repo
- Commit to repo
- Make release
- switch to alternate repo
- Make release
- switch back to primary repo

I think the only issue would be that the alternate
repo would have to have the same layout as the primary
repo. But you should be able to get that if you (a)
exported a release and made that the import of the
alternate's trunk, and (b) committed to the trunk of
the alternate and then made a release from the
alternate.

The process might get a little more muddy depending on
how well the tools handle the merging and such. At
worse case, you might have to check out your release
into a separate directory before doing the switch
process.

FYI - I am not 100% sure this will work - more like
25-50% sure. And wouldn't try it unless someone else
confirmed my line of thought; at least, not in your
normal WC with anything important.

The other alternative of just doing the export and
import into a branch on a separate repo will likely be
cleaner and easier to do though.

Just a thought & 2 cents for the pot.

BRM

--- Steve Greenland <steveg@lsli.com> wrote:

> On Mon, Jan 31, 2005 at 04:00:06PM +0000, abcd
> wrote:
> > --- Petr Smr??ka <smrcka@1sig.cz> wrote:
> > > There will be a trunk of the project accessible
> to
> > > your client
> >
> > That's precisely what I don't want to happen. The
> > client does not (and should not and will never)
> have
> > the visibility of my machines. Is your procedure
> > applicable even in the case of a completely
> > independent repository i.e., one residing on a
> remote
> > machine?
>
> In that case, I think you're stuck with the
> following model:
>
> - In your repo, on the trunk, hack hack hack.
>
> - Create a release for you client by copying to tag.
> (Or merge into
> client branch, or whatever is appropriate.)
>
> - Export the tag.
>
> - Import the export into client repo.
>
> Of course, by doing this, not much is gained by them
> having their own
> repo; you might as well give a tarball. Hmmm, I
> suppose them having a
> repo might make it easier to preview changes,
> revert, etc.
>
> Ahhh, the other approach might be SVK, which does
> support merging
> between repositories. But all I know about SVK I
> read on the web:
> http://svk.elixus.org/
>
> Steve
>
>
> --
> "Outlook not so good." That magic 8-ball knows
> everything! I'll ask
> about Exchange Server next.
> -- (Stolen from the net)
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail:
> users-help@subversion.tigris.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jan 31 18:24:31 2005

This is an archived mail posted to the Subversion Users mailing list.