On 4/6/06, Stefan Küng <email@example.com> wrote:
> Aaron Davies wrote:
> > OK, it looks like I may have been at least partially barking up the
> > wrong tree on this. In our layout, the "bin" folders (and all their
> > parents, of course) are in fact versioned, in the cases that are
> Then you can't ignore them.
> > showing up. However, the "bin/com" folders contained within them are
> > not. Shouldn't adding "bin/com */bin/com */bin/com/*" to the pattern
> > ignore these as well, or am I confused again? (It doesn't.)
> No. Because depending on what folder you're showing the status for,
> Subversion uses relative paths or even no paths at all. So when you're
> ignoring bin/com and Subversion checks the status inside the bin folder,
> it can't ignore the com folder because 'com' doesn't match 'bin/com'.
> And as I said, it depends on which path you right-clicked on to show the
> status: sometimes it really checks for the whole relative paths, so in
> those cases you *can* ignore the bin/com folder with that pattern, but
> not in all cases.
OK, now I get it. I think. The unversioned direct child of a versioned
folder is the first (and only) element of its own path, right? I.e.,
these unversioned com folders, children of versioned bin folders, are
just "com" for the purposes of pattern matching. Thus, ignoring "com",
no stars or slashes, should ignore it (which it does).
> > For reference, my entire ignore pattern is:
> > build deploy dist JuggerNet bin/com */bin/com */bin/com/* bin */bin
> > */bin/* obj *.dll *.pdb *.csproj.user *.suo _ReSharper*
> > *.resharperoptions *.class
> Why don't you use */com/* */com to ignore the com folder inside the bin
> > As you can see, this is a multi-language project using both Java
> > (built in Eclipse) and C# (built in Visual Studio). (Some of those
> > patterns are probably redundant (like obj); I been focusing on getting
> > all the files I want ignored, ignored, not optimizing the path.)
> What you should ask yourself here: why did you version the bin folder in
> the first place? Maybe you can reorganize your source tree to put *all*
> generated files into one folder and then just ignore that folder with
> the svn:ignore property (take our project as an example).
It looks like the bin folder is versioned in some cases so it can hold
a script that needs to be deployed. IOW, it's out of my hands.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Fri Apr 7 00:10:32 2006