[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Projects?

From: Robert Simmons <derisor_at_arcor.de>
Date: 2003-10-22 00:42:23 CEST

> "Michael Suess" <mike_ml@suessnetz.de> wrote in message
> Hash: SHA1
> On Wednesday 22 October 2003 00:08, Robert Simmons wrote:
> > [snip]
> > 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.
> This wont happen. The global revision numbers are tied to subversion and

Saying "that wont happen" rather defeats the purpose of a discussion group
doesnt it? Id like to at least discuss the pros and cons a bit before such a
decision is made. so far I havent heard any cons.

> although I am not a developer, I am pretty sure this is not going to change
> anytime soon. Especially since your projects can have any version numbers
> they like, its just their version in the repository that is incremented this
> way...

Oh yes I know that. But I want the revision of the project in the the repository
to reflect its overall change history. In fact, its a great tool for assesing
active versus passive projects as well as great number of other things. Its all
goodness from what I can see. I cant think of any bad points. If you have some,
lets hear 'em! =)

> > 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).
> Thats what mod_authz_svn is for. See the excellent INSTALL - File in
> subversion/mod_authz_svn/.
> Michael

And if I have a psycho network admin that doesnt want things running over HTTP
at all? Or I have a company where the web server MUST be IAS whether it is a
piece of doggy doo or not? What about the security hole of users and ssh
clients? What about the ... well I could go on forever.

There are a billion corporate policies. The only way to get a product into a
large number of corporations is to make it uber-flexile. That cant be done if
only one version of the interface supports authorization. Authentication needs
tobe done elsewhere, I wholeheartedly agree. However Auth should happen on the
server itself with options for binding to LDAP as well.

-- Kraythe

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:43:05 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.