Comprehensive Guide to SVN Directory Ignoring: From Basic Operations to Advanced Pattern Matching

Overview of SVN Directory Ignoring Mechanism

During software development, project directories often contain files and folders that don't require version control, such as compilation-generated cache directories and temporary files. Apache Subversion provides robust ignoring mechanisms to manage these contents, with the svn:ignore property serving as the core implementation.

Basic Ignoring Operations

To ignore specific directories, you need to set the svn:ignore property on the parent directory of the target. Consider the following project structure:

project/
    source/
    cache/
    other/

When located in the project directory, use the following command to ignore the cache directory:

svn propset svn:ignore cache .

This command means: set the svn:ignore property on the current directory (.) with the value cache. After execution, SVN will no longer track status changes for the cache directory.

Multiple Item Ignoring Configuration

When multiple directories or files need to be ignored, you can use an external editor to set property values:

svn propedit svn:ignore .

In the opened editor, each ignore pattern must occupy a separate line. For example, to simultaneously ignore cache, temp, and all .log files, input:

cache
temp
*.log

Note that patterns cannot be separated by spaces; line breaks must be used.

Recursive Ignoring Settings

To apply the same ignoring rules throughout the project tree, use the recursive flag:

svn propset svn:ignore -R "cache
temp
*.log" .

The -R parameter ensures ignoring rules are applied to the current directory and all its subdirectories. This is particularly useful in large projects to maintain consistent ignoring policies.

File Pattern Matching Mechanism

SVN's ignoring patterns support Unix-style filename wildcards:

• *: Matches strings of any length (including empty strings)
• ?: Matches any single character
• [abc]: Matches any one character within the brackets
• [a-z]: Matches any character within the specified range

For example, to ignore all temporary files, use pattern *.tmp; to ignore files with specific extensions, use *.{obj,exe,dll}.

Property Management Commands

View currently set properties:

svn proplist -v

Get values of specific properties:

svn propget svn:ignore

Delete ignoring properties:

svn propdel svn:ignore

Advanced Configuration Techniques

For complex ignoring requirements, use files to manage pattern lists. Create a .svnignore file:

cache
temp
*.log
*.tmp
build/

Then set properties using file mode:

svn propset svn:ignore -R -F .svnignore .

This method facilitates team collaboration, as the .svnignore file can be included in version control to ensure all developers use the same ignoring rules.

Common Issues and Solutions

Issue 1: Ignoring rules not taking effect
Check if properties are set on the correct parent directory and if patterns are written correctly. Directory names should not contain slashes; use cache instead of cache/ or /cache.

Issue 2: Versioned files cannot be ignored
SVN's ignoring mechanism only works for unversioned files. If files have already been added to version control, you need to remove them using svn delete command before they can be ignored.

Issue 3: Recursive settings causing over-ignoring
When using the -R parameter, ignoring rules apply to all subdirectories. If certain subdirectories require different ignoring strategies, set properties separately on those directories.

Best Practice Recommendations

1. Define ignoring rules early in the project to prevent accidental commits of unnecessary files

2. Use file patterns to manage complex ignoring rules for easier maintenance and team sharing

3. Regularly check ignoring settings to ensure no important unversioned files are missed

4. In team projects, include ignoring configuration files in version control to ensure consistency

Conclusion

SVN's directory ignoring functionality is a crucial tool in version control management. By properly utilizing the svn:ignore property, developers can effectively manage non-versioned content in projects. From basic single directory ignoring to complex pattern matching, SVN provides flexible configuration options to meet various project requirements. Mastering these techniques will significantly improve the efficiency and accuracy of version control management.