RE: Re: Global Ignore Pattern Issues

 
"
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).
"

Listen up folks! This should be standard practice by now for anybody who is responsible for/involved with build practices...

So many headaches, so much wasted time, because this is not done!-(

Unfortunately, we inherited a large protect with the same problem (poop everywhere).

And, um speaking of which, I hate to say it, but projects shouldn't be self centered either. The "generated" files of svn can wreak havoc on other tools that don't necessarily think having a global ignore/exclude list is a normal part of configuration (a million and one art tools for example, other build tools, etc).

$0.02

Sorry for the semi-off-topic rant!-)
Peter

-----Original Message-----
From: Stefan Küng [mailto:tortoisesvn@gmail.com]
Sent: Thursday, April 06, 2006 1:16 PM
To: users@tortoisesvn.tigris.org
Subject: Re: Global Ignore Pattern Issues

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.

> 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 folder?

> 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).

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org