> > Pro & Con:
> > + uses already done code from libsvn_fs, with minor modifications.
> > + possibly allows for restructuring of libsvn_wc, which is a fragile
> > piece of work (at least that's my impression reading the mailing list) +
> > That solves some issues, at least the four above.
> > + It may be a performance improvement.
> > + It should save some space. On a 4k filesystem the
> > ~ the current way could be left, as it's much easier for moving wc's
> > around. (although I don't really buy the point - who can move wc's can
> > update a pointer in a ~/subversion/-file.
> > - changes to current architecture are needed.
>
> con: the WC loses platform independence (i.e., you can't share it and
> expect it to work under linux, mac, and windows).
I'd expect to have a processor-dependence, ie. big vs. little-endian.
Is the db-format different between linux/windows/MacOS/etc.???
Regards,
Phil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Feb 10 12:18:04 2004