Re: [REQ] WC-only properties (local:)

On Oct 3, 2004, at 5:07 PM, Julian Foad wrote:

> + you didn't seem to give a concrete example of something being made
> much easier by your new properties (the example above about some
> script is not detailed enough for us to see the usefulness of it);

Here's another example. I have a Makefile for an Xcode project in a
repository. The Makefile is so I can svn update and build and install
changes without having to open up Xcode. Anyway, it assumes 2 things:
that your built products are put in the build directory instead of
somewhere else, and that you want the built application to be installed
in ~/Applications. It would be nice to be able to use local: properties
to specify build products and final location if different from the
assumptions. Currently anybody who needs this has to modify the
Makefile and then avoid committing it to the repository on any future
commits. Having local: properties would be very handy here.

> + the suggestion immediately looks like it has many open questions and
> awkward interactions (e.g., do these new properties get copied by "svn
> copy"? reported by "svn diff" as themselves and/or as the properties
> that they shadow?).

What I was thinking was they'd act just like regular properties except
they don't live in the repo, so svn copy would copy them, etc. svn diff
wouldn't report them since there's nothing to diff against.

Your comment about shadowing makes me thing I wasn't clear about
something. A local:svn:ignore property doesn't shadow svn:ignore per
se, since in this case you'd probably want it to be added to the ignore
list and not replacing the ignore list (although, say,
local:svn:eol-style would replace svn:eol-style). Shadowing like that
would imply any time you read svn:ignore it would check
local:svn:ignore and use that instead, and that would imply you could
never get the real value of svn:ignore without removing your
local:svn:ignore property. What I'm thinking is any code that uses
svn:ignore (and the other special properties) would check
local:svn:ignore (or the respective local: property) as well. That way
svn propget could still show the original value for svn:ignore yet
anything that uses it would use the local property too.

-- 
Kevin Ballard
kevin@sb.org
http://www.tildesoft.com
http://kevin.sb.org