[ I tried to add a comment to the issue but the site timed out on
submitting the form ]
chrismattmann_at_tigris.org wrote on Tue, Jun 28, 2011 at 13:53:08 -0700:
> http://subversion.tigris.org/issues/show_bug.cgi?id=3941
>
>
>
>
>
>
> ------- Additional comments from chrismattmann_at_tigris.org Tue Jun 28 13:53:07 -0700 2011 -------
> > I'll reopen this. My current workaround suggestion would be for you to add
> > '*.pyc' to your global-ignores list (in the runtime configuration area),
> > understanding that that will effect all the working copies you interact with >
> on that computer.
>
> Oh, thanks I hadn't thought of that!
>
> > Also, we've had discussions in the past about inheritable properties. It
> > seems reasonable (to me, at least) that one solution to this would be to
> > implement inheritable properties, which you would set on your working copy
> > but which would apply recursively to the externals directories.
>
> +1, sounds like it could work.
>
> > Finally, I've been unhappy about the fact that our svn:externals property
> > values don't carry a format specifier, which really ties our hands in terms of
> > compatibility across changes to that format. Had we been smart enough to add
> > such a thing, we could more easily expand that format into some sort of
> > structured document syntax that would allow you specify things such as
> > "additional ignores to apply to the external".
>
> Yeah something like this is what I was thinking about with Greg. Like wouldn't
> it be nice if I could define something like:
>
> property: svn:external-ignores:foodir
> value: *.pyc
>
> Then when pulling in an svn:external named foodir, we could check to see if this
> property was defined and then filter on incoming files using the svn:ignore
> value for it.
>
Or
svn propset svn:ignore 'external-dir/*.pyc' ./
(which nicely parallels the fact that svn:externals can be set at
a non-immediate parent)
Received on 2011-06-29 01:46:18 CEST