[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: keeping a photo library in a svn repository

From: John Niven <jniven_at_bravurasolutions.com>
Date: Wed, 6 Aug 2008 10:06:48 +1200

> -----Original Message-----
> From: sebastien.barthelemy_at_gmail.com
> [mailto:sebastien.barthelemy_at_gmail.com] On Behalf Of
> Sébastien Barthélemy
> Sent: Wednesday, 6 August 2008 01:31
> To: John Niven
> Cc: users_at_subversion.tigris.org
> Subject: Re: keeping a photo library in a svn repository
> Hello John,
> thank you for your reply.

No worries!


> ok, I agree with you. But if I want to view them, I'll need a
> checkout an export. And in order to add pictures I'll need a
> (maybe partial) checkout.

Not necessarily; if you use Apache (or ViewVC) you can browse the repository and view the images through a web browser. You could also use TortoiseSVN's repository browser (Windows only), or another client like RapidSVN, though these may be slightly more cumbersome (IMHO Apache makes this really, really easy. One of the things I like about Apache is that I can email URLs to people, pointing at files I have in SVN).

You *will* need a checkout to add new files, but this doesn't need to be resource or time consuming: you could create a new directory on the repository, checkout the (empty) reposity, and copy or move your new images to it, and finally do a commit. If you simply move your new images this shouldn't take up any more space than before, up to the point where you commit (at which point the ".svn" directories will be populated with copies of your images) - but with your images now in the repository you're able to delete the working copy (unless, of course, you want to continue editing the images).

> If I keep the repository on my computer, I don't really those
> as all the information is available in the repository. Do you
> know if I can bypass that ?

I'm not sure I understand? I think the answer is not really, excepting direct access to the repository (via Apache, etc).

> maybe a versioned filesystem would be more suited. I'll have
> a look at svnfs.

Quite possibly; I haven't looked at svnfs but will now go off and google for it! Thanks for the pointer!


> > what you will lose (though I suspect it won't affect you)
> is the ability to merge changes if two or more people work on
> the photo at the same time. If this is the case you'll need
> to look at SVN's locking mechanism to prevent multiple users
> from modifying the file simultaneously.
> thank you for rising this problem. I think you're right, it
> will be fine indeed.

To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-08-06 00:07:36 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.