Revision storage question

[Angela]

On 2/6/07, John Arbash Meinel <john at arbash-meinel.com> wrote:
>
> Angela wrote:
> > Actually, I think Bazaar isn't exactly what I'm looking for in this
> other idea
> > "repository" I'm looking at, mostly because these are
> directories/folders with
> > lots of files (majority of them binary files) and to checkout the whole
> "parent"
> > directory in order to work on one file remotely might not be a very good
> idea.
> > I was actually looking at Subversion for this (mostly because of the
> partial
> > checkouts idea) but feel very reluctant to be running two VCSs at the
> same time,
> > plus SVN feels quite a bit more complicated than Bazaar to me -- more
> > "permanent", with all the talk about SVN servers and repositories and
> making
> > sure your repository has a filesystem that will stay good a few years
> down the
> > line.
> >
> > Angela
>
> You can break things up into a more fine grained set of branches, so
> documentation for project 1 is a separate branch then documentation for
> project 2.
>
> But whatever the layout we don't really support checking out just one
> file/subdirectory of a project like SVN supports. For lots of projects
> this is a net consistency win. It is pretty easy to have a tree in a
> weird state with CVS/SVN because you committed some files and someone
> else committed other (non-overlapping) files.
>
> There is still the issue of needing to download the history for file X
> when you are only editing file Y.
>
> There are 2 solutions to this. First you can use a lightweight checkout
> (bzr checkout --lightweight). Which won't download the history of files,
> and acts more like a CVS/SVN checkout (diff has to connect to the server
> to get the old text, commit, log, annotate must connect to the server,
> etc).
>
> You still have a little bit more overhead than with SVN because you
> can't checkout a single file.
>
> The other solution is to have a local shared repository (bzr init-repo
> --trees PATH). Whenever you do a checkout/branch underneath PATH it will
> store the history files at PATH/.bzr/repository. Which means that you do
> still need to download all the history, but only once. You don't have to
> download everything for each new checkout, even after getting rid of the
> checkout.
>
> John
> =:->
>
>
Hello John,

Thanks for your suggestions. Basically the problem right now is that there
are a few couple directories that need versioning, and they contain binary
files. All in all the size right now is up to ~800MB, and I've broken it
down to four chunks. Each chunk has a dozen or two subdirectories under it,
and a still a few under _that_, etc. One could say that it makes more sense
to create repositories for smaller chunks than the four (i.e., instead of a
repository for all documentation on a project, you'd have one repository for
the technical documentation, another repository for the user's manual, etc)
although I'm still debating the pros and cons of that one -- looking at it,
that's a lot of repositories shared over the network.

I'd like to clarify the last solution you mentioned, about a local shared
repository. I did that with the actual project, but since Bazaar works
rather transparently (plus the shared repository has just started) I haven't
been able to notice any marked difference between that and not having a
shared repository. How would it impact my (large) repositories right now if
I accessed them via the network (getting checkouts from another computer on
the network, storing *my* history in a local shared repository, and then
committing both on local and the other computer)?

Thanks!


-- 
And I write in my seasonal plume.
http://seasonalplume.net
http://indisguise.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/bazaar/attachments/20070207/2dffb49a/attachment.htm