I made a change yesterday to our sqlite support to enable readonly
operation. I'll work on ensuring it propagates out to the cmdline.
Cheers,
-g
On Sep 18, 2008, at 13:43, Martin Furter <mf_at_rola.ch> wrote:
>
>
> On Thu, 18 Sep 2008, Miha Vitorovic wrote:
>
>> dglasser_at_gmail.com wrote on 17.09.2008 16:07:24:
>>
>>> As this thread has gone on, I think I've lost track of the
>>> motivation
>>> for centralizing the metadata beyond just the working copy root. I
>>> understand wanting to be able to (optionally) centralize and share
>>> the
>>> blob-store (since file contents/etc are likely to be shared between
>>> multiple working copies), but what is the gain of combining the
>>> actual
>>> working copy metadata itself? (More than "you can control where it
>>> sits", which you can also do by replacing the .svn directory with a
>>> symlink.)
>>
>> As I explained in another thread, there may be cases where the source
>> files aren't on an actual disk and you can't create folders there.
>> It has
>> the potential to bring Subversion to places where it wasn't before.
>
> What do you mean with 'not on an actual disk'?
> You have them on a read-only filesystem?
> I also have working copies on read-only filesystems (NFS mounts to
> be able to compile on different machines), though I only need
> svnversion and 'svn info' there.
> I hope read-only operations will still be possible on read-only
> working copies.
>
> Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-09-18 19:53:25 CEST