Robert Simmons wrote:
> Once again, I am sorry if I'm hitting things that have been discussed but maybe
> they need to be discussed again. =)
>
> At any rate, I enjoy the new revision system in subversion except for one small
> detail. The problem is that with this revision I can t have two projects in the
> same repository without them both having the same revision number no matter how
> many times they have changed independently. The result is to create multiple
> repositories. However, there are situations where projects are related and
> should be located in the same repository.
Well, let's throw it back to you: Why do you need separate revision
numbers for each project? There are a huge amount of people using
systems like Perforce that use a single repository wide changeset
number, and they seem to get by. What's the big issue you have with it?
Generally, it seems that people's problem with it is psychological,
and in practice it isn't a real issue.
> What I would like to see is the concept of a project in the version control
> system where two projects can share the same repository and yet have different
> version numbers. You should be able to assign commit permissions on a
> per-project basis as well. (Although right now I don't even know how to assign
> authorization on repositories).
In subversion authorization happens at a higher level than the
repository (currently). Either at the repository access layer (inside
Apache for ra_dav, or (in theory) svnserve in ra_svn), or in a hook
script that gets run before commits. There have been discussions about
more complex access controls that would be built into the repository,
but it's a post-1.0 issue.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 22 00:17:37 2003