Michael L Brown wrote:
>
> I didn't find anything in the book (printed) that said keywords won't be
> screwed with if the file is listed as binary.
I looked and didn't see anything either.
>
> > svn propdel keywords --revprop -r 5
> >
> svn+rsh://rtpsvr1/ThirdPartyTools/trunk/Plugins/RaySearch/libOrbitPlugin.2.0g.so
>
>
> You're trying to remove a revision property when you should be changing
> a file property. There is no special meaning to a revision property of
> svn:keywords. Also, you can't change the file already in the
> repository, so your best bet is to update to HEAD, remove the property
> with 'svn pd svn:keywords ...../libOrbitPlugin.2.0g.so' and then copy in
> a known good copy.
>
> What I did is directly from the book, page 215 of the printed version,
> complete reference section.
Yes, page 215 is describing the correct subcommand (propdel), but the
command is using incorrect command line flags. The --revprop only
operates on properties that are for the entire revision, not for any
files or directories in the repository.
You can't remove or change file or directory properties without doing so
in your working copy and then commit.
> You still need to run
>
> svn pd svn:keywords ...../libOrbitPlugin.2.0g.so
>
> I said that I did.
Without the --revprop flag.
> and probably should run it on all binary files you have in your repository.
>
> Unfortunately, that won't fix any bad ones that are there. I'll have to
> find the bad ones and fix them up, one by one.
>
> > Whew! But, what needs to be done to keep this from happening again?
>
> Change your procedures so you only apply svn:keywords to everything in
> the repository.
>
> I think you mean to only apply it to text files that are checked in.
Yes! Typo there.
> Nice idea, but here is where SVN falters... no master config file and no
> master config file that would override any user config file. If I
> create a new config file and send out e-mail telling users to install it
> over their current config file, it might not get done. The fact that
> there isn't a master config in the repository area that is the end all
> to be all, is a real problem. Depending on users to keep their local
> copies up-to-date is not realistic.
>
> I'm guessing that I now need to figure out how to do this via a hook
> script.
Yes, to prevent commits that mix properties, you'll need a pre-commit
hook script.
Regards,
Blair
--
Blair Zajac, Ph.D.
<blair@orcaware.com>
Subversion and Orca training and consulting
http://www.orcaware.com/svn/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri May 20 00:17:32 2005