You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by SteveKing <st...@gmx.ch> on 2003/05/26 18:36:37 UTC
get version of repository
Hi,
Right now subversion doesn't provide a function to
get the version of a repository (or I havent' found
one). I already checked the mailing list and the issue
tracker but found nothing.
I would like that both server and client would exchange
those version information on connect. That way
both server and client could check if they are still
compatible and error out if they are not (I guess it will
always be the newest versioned part (server or client) which
will know if it's compatible or not).
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.
Also, for local repositories (no server) the client should be
able to check with which version the db was built and
especially with which version of the berkeley db it
was built and at least warn the user if those don't match.
Maybe create a file with those version numbers in it
when calling svn_repos_create() which could be read out?
I guess this file would then have to be updated when
doing an svnadmin dump/load?
Stefan
Re: get version of repository
Posted by "Glenn A. Thompson" <gt...@cdr.net>.
>
>
>>>
>>>
>>Are the changes in there getting pretty close to a merge with the trunk?
>>I kinda neglected keeping up with that branch. gat
>>
>>
>
>I could probably merge those changes today, but I anticipate more
>changes, and would like to buffer them all up as long as I can.
>
>
Otay, I guess I should get off my duff and go look at them. Or should I
say on my dufff:-)
gat
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: get version of repository
Posted by cm...@collab.net.
"Glenn A. Thompson" <gt...@cdr.net> writes:
> Hey,
>
> >I've already got some pending changes in my fs-schema-changes branch,
> >and there are likely to be more. Unfortunately, no docs.
> >
> Are the changes in there getting pretty close to a merge with the trunk?
> I kinda neglected keeping up with that branch. gat
I could probably merge those changes today, but I anticipate more
changes, and would like to buffer them all up as long as I can.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: get version of repository
Posted by "Glenn A. Thompson" <gt...@cdr.net>.
Hey,
>I've already got some pending changes in my fs-schema-changes branch,
>and there are likely to be more. Unfortunately, no docs.
>
>
Are the changes in there getting pretty close to a merge with the trunk?
I kinda neglected keeping up with that branch.
gat
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: get version of repository
Posted by cm...@collab.net.
Edmund Horner <ed...@chrysophylax.cjb.net> writes:
> > 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.
>
> Do the core Subversion developers have ideas for improvements to the
> schema (apart from DB-independence) ? Is there a doc I can go read?
I've already got some pending changes in my fs-schema-changes branch,
and there are likely to be more. Unfortunately, no docs.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: get version of repository
Posted by Edmund Horner <ed...@chrysophylax.cjb.net>.
> 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.
Do the core Subversion developers have ideas for improvements to the
schema (apart from DB-independence) ? Is there a doc I can go read?
Thanks,
Edmund.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: get version of repository
Posted by Branko Čibej <br...@xbc.nu>.
SteveKing wrote:
> Hi,
>
> Right now subversion doesn't provide a function to
> get the version of a repository (or I havent' found
> one). I already checked the mailing list and the issue
> tracker but found nothing.
svn_repos_open will check the repository version. However, up to now, we
have never changed the version number: the schema changed too many
times, and we do have a pre-1.0 compatibility policy documetned.
> I would like that both server and client would exchange
> those version information on connect. That way
> both server and client could check if they are still
> compatible and error out if they are not (I guess it will
> always be the newest versioned part (server or client) which
> will know if it's compatible or not).
I think it might be a bit more complicated than that. Server and client
should exchange a list of capabilities, like they do in ra_svn.
> 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.
(Personally, I only had to go through one update till now; moved 30
people from 0.14.1 to 0.21.0, with no problems at all.)
> Also, for local repositories (no server) the client should be
> able to check with which version the db was built and
> especially with which version of the berkeley db it
> was built and at least warn the user if those don't match.
This is already done, both at compile time and at run time. the FS layer
will error out if it's running under a different BDB version than it was
compiled against.
> 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 it?
> 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 schema.
--
Brane Čibej <br...@xbc.nu> http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org