WorkingTree doesn't expose API for ignore/unignore

[Jeff Bailey]

WorkingTree provides interfaces to tell if a file is ignored or not, but doesn't expose an API to twiddle that setting.

Robert said on IRC that he considered this to be a bug, so I'm filing it as such.

Tks,
Jeff Bailey

[John A Meinel (jameinel)]

Agreed. Right now the only way is to write .bzrignore directly. And this is extra bad if we decide to use a different layout in the future.

[Dan Watkins (oddbloke)]

The way ignores work currently, as I understand them, is that .bzrignore gets read in when it is needed. It is cached internally until unlock() is next called, when the cache is cleared.

If we allow manipulating of ignore definitions through the WorkingTree, we will need to write the definitions back out when unlock() is called. What happens if .bzrignore has been edited between the locking and unlocking?