Re: Breaking up a monolothic repository

2013-09-08 Thread Thorsten Schöning
Guten Tag Trent W. Buck, am Montag, 9. September 2013 um 03:13 schrieben Sie: > What else can I do? Tell us about the size of your repo, it's format version and primary data types versioned, as you always can simply clone the entire repo into one for each project needed and delete and move unneed

Re: Breaking up a monolothic repository

2013-09-08 Thread Trent W. Buck
Geoff Field writes: >> I get the impression that $company's projects mostly have a finite >> lifespan (a couple of years), > > By "lifespan", what exactly do you mean? At my company, the > individual projects might be in production within anywhere from 6 > months to 2 years after start of develo

RE: Breaking up a monolothic repository

2013-09-08 Thread Geoff Field
> From: Trent W. Buck > Sent: Monday, 9 September 2013 12:17 PM > Nico Kadel-Garcia writes: > > > Lock the existing repo: Do clean exports, and imports, to new > > repositories with the new layout, with a README.md or other > guideline > > to where the legacy repository exists. You lose the in

Re: Breaking up a monolothic repository

2013-09-08 Thread Trent W. Buck
Nico Kadel-Garcia writes: > Lock the existing repo: Do clean exports, and imports, to new repositories > with the new layout, with a README.md or other guideline to where the > legacy repository exists. You lose the infinitely preserved history this > way, but for most working software projects,

Re: Breaking up a monolothic repository

2013-09-08 Thread Nico Kadel-Garcia
Lock the existing repo: Do clean exports, and imports, to new repositories with the new layout, with a README.md or other guideline to where the legacy repository exists. You lose the infinitely preserved history this way, but for most working software projects, you don't *need* that. And it's a go

Breaking up a monolothic repository

2013-09-08 Thread Trent W. Buck
I have inherited a single monolithic repo for all the company's projects. I want to migrate to one repo per project. (One-way, one-time migration.) Following the red-bean book[0], I first tried svnadmin, which was really slow, and eventually crashed because some files were copied into projects/13

Re: libsvn_ra_serf/util.c: undefined reference to serf_bucket_request_set_CL [1.8.1][1.8.3][WORKAROUND]

2013-09-08 Thread Nico Kadel-Garcia
This is why you either update a system version that is high enough, or you use the "get-deps.sh" to pull down versions locally and compile them statically. I've been publishing up-to-date get-deps.sh, slightly more consistent in layout and up-to-date, at https://github.com/nkadel/subversion-1.8.x-s

Re: svn 1.8 causing locks to be broken on update

2013-09-08 Thread Branko Čibej
On 08.09.2013 11:03, Felipe Alvarez wrote: > You could try one of these (i386 versions are also available): > > > http://opensource.wandisco.com/centos/5/RPMS/x86_64/ > > They're made fore CentOS, but AIUI, should work on RHEL as well. > 1.6.17 isn't there, but newer versions are; I'd s

Re: svn 1.8 causing locks to be broken on update

2013-09-08 Thread Felipe Alvarez
You could try one of these (i386 versions are also available): > > http://opensource.wandisco.com/centos/5/RPMS/x86_64/ > > They're made fore CentOS, but AIUI, should work on RHEL as well. 1.6.17 > isn't there, but newer versions are; I'd suggest trying the latest, > 1.6.23-2. > Are these "Apache