[SM-Discuss] SCM perforce replacement was: Re: Grimoire Team Lead vote
afrayedknot at thefrayedknot.armory.com
Thu Mar 16 11:44:01 EST 2006
On Wed, Mar 15, 2006 at 11:45:30PM +0100, Pieter Lenaerts wrote:
> Op wo, 15-03-2006 te 09:32 -0800, schreef Andrew:
> I think this is of course a good reason to go for distributed forced
> with a central repository. The main concern then becomes the size of the
> repositories imo. Can we somehow get an estimate on the size of the
> grimoires + their history? I'm a bit afraid that this would put a
> serious burden on diskspace for gurus, but I don't know just how big it
> would be...
That I dont know, however scms tend to be relatively efficient this way. I
know arch based stuff stores 4 or 5 files per change (regardless of the
number of files). What they suggest is to "roll-over" your repository
every year, basically do a branch from head-of-line to a new 'archive'. At
which point it will remember where it branched from, but not require
carrying all the years patches with it. Other scm's can of course do
the same thing, just "branch" at some point.
Im pretty sure bzr has a 1:1 ratio for file to files for revision
storage. Each file has another file that contains its revision history.
> > --- onto alternatives
> > Bzr is pretty nice, looking at the competition it's definitly at the
> > front of the pack right now. I was following their development for a
> > while but stepped away for a while. The main issues I found with it
> > boiled down to lack of a remote submits. They seem to at least have a
> > push command now which might be enough to eliminate that issue. The only
> > other thing that comes to mind is support for cherry-picking, but thats
> > probably not an insurmountable issue.
> I'll install a bzr-ng sandbox on my server then. don't know how long
> this will take me to setup and regulate access to it.
cp grimoire to_dir
bzr add .
Then publish to_dir via http, or ftp or sftp.
> this sucks
> > An
> > active development community is definitly something I think is important
> > criterion.
> I think most of the scm's we talk about have an active community, no?
Most. Actually my favorite scm (ive tried to remain neutral throughout
this), is ArX. ArX is a fork of gnu-arch, and it actually does pretty
much everything i need (which is similar to what arwed listed). In
particular it can do cherry-picking properly in most cases, its not as
good as perforce, but its better than almost anything else I tried.
The major downside i see is theres a small development/userbase. I think
theres one guy maintaining it. Thats of course fine for now since its
mostly bug-free and in maintainence mode. But it makes me nervous.
| Andrew D. Stitt | acedit at armory.com | astitt at sourcemage.org |
| irc: afrayedknot | Sorcery Team Lead | ftp://t.armory.com/ |
| 1024D/D39B096C | 76E4 728A 04EE 62B2 A09A 96D7 4D9E 239B D39B 096C |
More information about the SM-Discuss