RE: Bikeshed: configuration override order
> -----Original Message-----
> From: Julian Foad [mailto:julian.foad_at_wandisco.com]
> Sent: Tuesday, August 10, 2010 6:25 PM
> To: C. Michael Pilato
> Cc: Bolstridge, Andrew; Subversion Development
> Subject: Re: Bikeshed: configuration override order
> Oh? All I know about Andrew's particular requirements related to this
> query is what's quoted above - "If I ... accidentally leave the banned
> buildlog.htm file in ..." - which sounded vaguely like a requirement for
> a path-based rule. Maybe I missed something.
Drats! My hopes that an invalid commit might go faster because I'd made a mistake in understanding the hooks was cruelly dashed.
In a way it is a path-based rule - I want certain file extensions (eg. *.obj) , certain directories (eg Debug) and certain explicit files (eg buildlog.htm) to be barred from the repo. I used buildlog.htm as an example because it's easy to flip through the list to commit and mark the obvious ones off, but not so easy to keep all htm files, except that one.
Still, the client global-ignores is great, I just want to store it on the server.
The second aspect: client-stored passwords, this isn't so much about storing them on the client but about having different ones. Enterprises want single-signon, ie, a single password, centrally held, that is used for all apps. They don't really care about storing it locally so much as caring when Mildred calls the helpdesk to say her password doesn’t work only to find she's changed her main login but her svn password is the old, different one. I don't think there's much to do here, except to get LDAP working. Fortunately, VisualSVN allows integrated authentication with Active Directory, and most enterprises still use Windows.
It's still all about centrally-held configuration and not having to discover what a client may or may not happen to be using.
Received on 2010-08-11 11:06:50 CEST
This is an archived mail posted to the Subversion Dev