>>----- Original Message -----
>>From: "Branko Čibej" <email@example.com>
> This would make problems with incompatibilities non-existent
>>>>because a clear error message (e.g. "you need to update your
>>>>client to access this server") will prevent the user from
>>>>corrupting something in the repository/working copy.
>>>Well, that wouldn't make incompatibilities non-existent. :-)
>>>I also don't believe it's viable before 1.0, or at least until our final
>>>FS schema changes go in. Right now, the compatibility rule we have (one
>>>version etither way) is the best we can do, IMHO. Server admins should
>>>just make sure that people are using new enough clients.
> And that's exactly the problem. It's easily done inside a LAN where
>the admin has control over the clients. But imagine a public
>repository where you don't have that control (e.g. sourceforge.net).?
>Personally I don't think that this should be done after 1.0 but before
>since this feature is especially useful during the development phase
>of subversion where changes to client/server are more likely than
Hm. You have a point. This is somethign that would have to be exposed by
the RA layer...
Actually, for ra_dav, I think you can already do a client version check
on the server, using Apache config directives.
> Maybe create a file with those version numbers in it
>>>>when calling svn_repos_create() which could be read out?
>>>The BDB version numbers? But that's entirely the FS's business, isn't
>Sure, you're right. Do you know if the actually do?
I'm not sure we're talking about the same thing. Did you mean the BDB
version that the FS layer was linked agains should be available for
inspection, or the repository version, or the Subversion version number?
>>>>I guess this file would then have to be updated when
>>>>doing an svnadmin dump/load?
>>>I don't understand this. We already have a dump format version in the
>>>dump file. The dump format is theoretically independent of the FS
>what I meant is if a file with a version is placed in the repository and you
>do a svnadmin dump/load to update the repository to a newer version then
>the file with the version number in it should be updated.
Oh. If you create a new repository, it gets the new repository version
Brane Čibej <brane_at_xbc.nu> http://www.xbc.nu/brane/
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Mon May 26 23:20:26 2003