On 2/8/07, <b class="gmail_sendername">John Arbash Meinel</b> <<a href="mailto:john@arbash-meinel.com">john@arbash-meinel.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> Thanks for your suggestions. Basically the problem right now is that there<br>> are a few couple directories that need versioning, and they contain binary<br>> files. All in all the size right now is up to ~800MB, and I've broken it
<br>> down to four chunks. Each chunk has a dozen or two subdirectories under it,<br>> and a still a few under _that_, etc. One could say that it makes more sense<br>> to create repositories for smaller chunks than the four (
i.e., instead of a<br>> repository for all documentation on a project, you'd have one repository<br>> for<br>> the technical documentation, another repository for the user's manual, etc)<br>> although I'm still debating the pros and cons of that one -- looking at it,
<br>> that's a lot of repositories shared over the network.<br><br>They can be put in a fully shared repository, and just have separate<br>branches for everything. Clients will only download the portions they<br>need. For example:
</blockquote><div><br>Thanks! For now that's what I've done, but with trees; that
computer is used as actual file storage as well, so trees worked fine,
I think. Right now I have:<br><br>Documentation/<br>Documentation/.bzr/
<br>Documentation/Project1<br>Documentation/Project2<br>Documentation/Project3<br><br>Source/<br>Source/Project1/<br>Source/Project1/.bzr/<br>Source/Project1/live<br>Source/Project1/stable<br>Source/Project1/devt<br>Source/Project2/
<br>
Source/Project2/.bzr/<br>
Source/Project2/live<br>
Source/Project2/stable<br>
Source/Project2/devt<br><br>And
so on. :) I think this works good for me. I toyed with the idea of
having the whole root of the drive as a shared repository and just
define branches under it, but then I do have a few directories that I
don't want versioned (Installers, Images, personal stuff, etc) and
wasn't sure what impact having those non-versioned directories inside
might have on the shared repository. Additionally, I had already
started versioning the Source folder, with the shared repository on a
per-project basis, and wasn't sure how having a shared repository
within another shared repository work (I'm thinking it wouldn't). Or,
how to move history of a repository into a shared repository.
<span class="q"><br><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">For something like this, it does seem that 'bzr checkout --lightweight'
<br>may be your best method. This is very much 'SVN' mode, since you don't
<br>have any history stored locally. (It does mean that you can't commit<br>while offline, but that doesn't sound important in your situation).</blockquote></span><div><br>No,
it's not that critical, at least for the documentation part; I'm
planning to do lightweight checkouts for documentation, and then
heavyweight checkouts for source/coding/programming. :) And yes, things
have been split up into smaller, more manageable chunks; I think the
biggest at the moment is 200MB.
<br></div><span class="q"><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I would definitely recommend using 'bzr+ssh://' if you can install bzr
<br>on your server, as it is already quite a bit faster than sftp, and with<br>what has been going on on the 'hpss' branch, it should continue to<br>become much better.</blockquote></span><div><br>I've
been reading into the bit of info on the bazaar server yesterday, but
haven't gotten anything conclusive yet about if I'll keep using bzr the
way I'm using it now, or to use the smart server. Right now, to do a
checkout on my laptop, I do:
<br><br>bzr checkout \\Server\source\project1\devt<br><br>(Actually,
I'm making a batch file for the less volatile documentation
repositories, but as of the moment that's the sort of command I'm using
for the batch file to retrieve/etc checkouts.)
<br><br>Would using the smart server be a better option? I can always install it as a service on the server computer if needed.<br><br>(PS.
The "server computer" I'm referring to is really basically an ordinary
desktop computer, not an actual server. It has Apache 2.2 plus PHP and
MySQL all that, but it's really for development/storage/everything else
purposes.)<br></div><br>Thanks again, you're great help. :D</div></div><br>Angela<br><br clear="all"><br>-- <br>And I write in my seasonal plume.<br><a href="http://seasonalplume.net">http://seasonalplume.net</a><br>
<a href="http://indisguise.org">http://indisguise.org</a>