Mike Brown (Michael.L.Brown@Philips.com)
Lotus Bloats: Michael L Brown/MSN/MS/PHILIPS
Philips/ADAC, Madison, WI
Desk: 608-288-6969 Fax: 608-298-2101
PMS direct: 164-6969
You design it, I'll build it!
Branko ╚ibej <firstname.lastname@example.org> wrote on 05/24/2005 12:41:06 PM:
> Michael L Brown wrote:
> >We DO NOT want users setting these properties. We want it transparent
> >to them. This kind of property setting can be done automatically, but
> >SVN doesn't allow that to easily happen. Users screw up constantly.
> >Give them the rope and they will hang themselves and I have to end up
> >fixing it.
> Have you heard of autoprops? They're a client-side config option at the
> moment, but you can certainly create autoprop configuration scripts that
> all users must add to their Subversion config. That eliminates users'
> setting the props by hand.
I believe you are talking about /etc/subversion config that must be placed
onto each client. Not viable, too many machines to manage. Trying to
sure that the users install a .subversion/config file is also error prone.
SVN should be able to manage a GLOBAL repository configuration, of which
the facility does not exist.
The lines I believe you are thinking of look like:
enable-auto-props = yes
* = svn:keywords=Id LastChangedDate LastChangedRevision LastChangedBy
The above is what got me into trouble in the first place. I can easily
change the single line into four lines, starting with: *.c *.cc *.h *.sh
in order to cover the known extensions. As I pointed out in previous
postings, the "tons" of shell scripts that we have do not have an
extension. We are Unix, so we don't necessarily do the WindBloze
extension thing. So, there is no way to wildcard pattern the tons
of shell scripts that we have.
Hopefully now you can understand our need for a way to say that binary
files should not have svn:keywords property settings. By having a config
that says to ignore a list of properties, then an "*" wildcard can be
used to cover all of the other files.
Now I have to write (a) hook(s) that look at each file (if it is not a
known binary in a list that I have) to find out if it is a shell script
or not. Something I don't really want to do, but have to.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Tue May 24 22:07:41 2005