You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Garrett Rooney <ro...@electricjellyfish.net> on 2004/05/03 01:03:41 UTC
Repository format file and multiple fs backends
How are we planning on handling repository format changes now that
there are multiple filesystem backends? The format file as it stands
just holds the version for the bdb filesystem, and has nothing to do
with the fsfs filesystem.
Perhaps we should find some way to transition to a filesystem backend
specific system for indicating what version of the repository schema is
in use. That certainly seems better than screwing things up for all
the fsfs users the next time we need to bump the bdb filesystem schema
version, or vice versa.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Repository format file and multiple fs backends
Posted by Edmund Horner <ch...@chrysophylax.cjb.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Garrett Rooney wrote:
| How are we planning on handling repository format changes now that there
| are multiple filesystem backends? The format file as it stands just
| holds the version for the bdb filesystem, and has nothing to do with the
| fsfs filesystem.
|
| Perhaps we should find some way to transition to a filesystem backend
| specific system for indicating what version of the repository schema is
| in use. That certainly seems better than screwing things up for all the
| fsfs users the next time we need to bump the bdb filesystem schema
| version, or vice versa.
|
| -garrett
What about format-specific data? For example, if I ever get back to
work on my SQL implementation (sit rep: thinking of translating to
PostgreSQL), I'd like a bit of guidance on where in the directory things
like server, username, password, and database should be stored. (Though
I suppose that a separate db/sql-config file or something is good enough.)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFAlaK0EbvImmpUq7gRAt7+AJ9GM19i5C+rP3j2wRE3pA7wMPgtUACfS6ys
ErEdDxp8bIyJW0x8yYdXEeE=
=BNBM
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Repository format file and multiple fs backends
Posted by Greg Hudson <gh...@MIT.EDU>.
On Sun, 2004-05-02 at 21:03, Garrett Rooney wrote:
> Perhaps we should find some way to transition to a filesystem backend
> specific system for indicating what version of the repository schema is
> in use. That certainly seems better than screwing things up for all
> the fsfs users the next time we need to bump the bdb filesystem schema
> version, or vice versa.
Sure. Associating the repository format file with the FS format is a
layering violation.
The next time we need to bump the FS format version (I don't think we
really have consensus on whether we can do that before 2.0), we can add
a format file to the relevant FS directory. The repository format file
will refer to the repository format, although we don't really expect to
change that incompatibly in the forseeable future.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org