On Thu, Dec 12, 2002 at 07:02:22PM -0500, Greg Hudson wrote:
>
> In <20021212141542.A1280@answerfriend.com>, mbk wrote:
> >typedef struct
> >{
> > const char *url;
>
> The repository for a URL varies depending on how you access it; you
> might use file:, http:, and svn: to access the same repository. I think
> we should avoid storing any data in one repository about another
> repository, with the exception of the guid.
>
I think that would make repository synchronization difficult.
The mapping between UUID and URL has to be stored somewhere,
so that a process can, based on the repos UUID of a node in the database,
go look for updates.
> > const char *name;
> > const char *short_desc;
> > const char *long_desc;
>
> So each repository contains a directory of descriptive information about
> a bunch of repositories? I don't like that at all.
I think this is useful information that can easily be kept up-to-date as
part of a synchronization operation. It would be nice to be able
to have something like
$ svnadmin repos ls
CollabNet:SVN the canonical subversion repository
Local things on my laptop
Sourceforge a free hosting service for open-source projects
$ svnadmin repos sync CollabNet Local
Connecting to CollabNet (http://svn.collab.net/repos/svn)
Connecting to Local (svn://localhost/)
Synchronizing....
> > const char *privkey;
>
> What would this be used for, and (as Branko tried to ask) why would a
> repository know any private key other than its own?
>
I don't think that's what he was asking. I think he was objecting to it
being stored in BDB at all, rather than in a file. This field would
certainly be null for other repositories (one more reason not to keep
it in BDB, I guess).
--ben
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Dec 13 16:03:22 2002