One data set - two repositories?

[cl...@qgenuity.com]

Hello,

I'm looking for a way to use Subversion to store data from a single data
set across two repositories. More specifically, I want to have one
repository which contains all of the data and a second that contains only
specific directories.

When I am at home, I will sync to the "complete" repository and when I am
traveling, I will sync to the "partial" repository.

How do I set this up so that the two repositories play nicely with each
other?

I willing to upgrade to whatever version of subversion makes the most sense.

Thanks in advance,
Jonathan
(please cc me directly as I am not subscribed to the list.)

Re: One data set - two repositories?

[Phil Pinkerton <ph...@philpinkerton.com>]

Create two working working copies as you described then up date the one your working on and commit after making changes. i.e 'complete' for home 'partial' for travel.


Sent from Phil's iPad

> On Oct 29, 2014, at 3:33 PM, Andreas Stieger <an...@gmx.de> wrote:
> 
> Hello,
> 
>> On 29/10/14 21:07, cl@qgenuity.com wrote:
>> I'm looking for a way to use Subversion to store data from a single data
>> set across two repositories. More specifically, I want to have one
>> repository which contains all of the data and a second that contains only
>> specific directories.
>> 
>> When I am at home, I will sync to the "complete" repository and when I am
>> traveling, I will sync to the "partial" repository.
>> 
>> How do I set this up so that the two repositories play nicely with each
>> other?
> 
> svn being a centralized system, the disconnected two-way element of your
> scenario is not part of its design. The keywords below will help you
> work around:
> a) svnsync, (one way) which has provisions for partial syncs
> b) same, but switching the direction as required
> c) two repositories with remote merging
> d) two repositories with vendor branches
> 
> Andreas
> 

AW: One data set - two repositories?

["Niemann, Hartmut" <ha...@siemens.com>]

> When I am at home, I will sync to the "complete" repository and when I 
> am traveling, I will sync to the "partial" repository.
Even easier:
one repository, two working copies.
Set the checkout depth to "empty" for all directories in the "traveling" working copy
that you don't want to sync when you are on the road.

Mit freundlichen Grüßen
Dr. Hartmut Niemann

Siemens AG
Mobility
MO MLT LM EN CCI 1
Werner-von-Siemens-Str. 67
91052 Erlangen, Deutschland
Tel.: +49 9131 7-34264
mailto:hartmut.niemann@siemens.com

Re: One data set - two repositories?

[Les Mikesell <le...@gmail.com>]

On Wed, Oct 29, 2014 at 5:33 PM, Andreas Stieger <an...@gmx.de> wrote:
> Hello,
>
> On 29/10/14 21:07, cl@qgenuity.com wrote:
>> I'm looking for a way to use Subversion to store data from a single data
>> set across two repositories. More specifically, I want to have one
>> repository which contains all of the data and a second that contains only
>> specific directories.
>>
>> When I am at home, I will sync to the "complete" repository and when I am
>> traveling, I will sync to the "partial" repository.
>>
>> How do I set this up so that the two repositories play nicely with each
>> other?
>
> svn being a centralized system, the disconnected two-way element of your
> scenario is not part of its design. The keywords below will help you
> work around:
> a) svnsync, (one way) which has provisions for partial syncs
> b) same, but switching the direction as required
> c) two repositories with remote merging
> d) two repositories with vendor branches

Or, if you are only concerned with committing/updating certain
subdirectories in a working copy when traveling, you don't need
different repositories for that.  Just do what you need.
You could even make different 'top level' projects that that pull in
the directories you want via svn external properties.   Updating from
the top level would update the whole tree of external references, but
you'd have to commit changes to them separately.

-- 
   Les Mikesell
     lesmikesell@gmail.com

Re: One data set - two repositories?

[Andreas Stieger <an...@gmx.de>]

Hello,

On 29/10/14 21:07, cl@qgenuity.com wrote:
> I'm looking for a way to use Subversion to store data from a single data
> set across two repositories. More specifically, I want to have one
> repository which contains all of the data and a second that contains only
> specific directories.
> 
> When I am at home, I will sync to the "complete" repository and when I am
> traveling, I will sync to the "partial" repository.
> 
> How do I set this up so that the two repositories play nicely with each
> other?

svn being a centralized system, the disconnected two-way element of your
scenario is not part of its design. The keywords below will help you
work around:
a) svnsync, (one way) which has provisions for partial syncs
b) same, but switching the direction as required
c) two repositories with remote merging
d) two repositories with vendor branches

Andreas