discussing ignore rules

[Wayne Davison]

On Thu, May 11, 2006 at 11:43:19AM +0200, Jan Hudec wrote:
> I don't, however, like the patch on different grounds. It adds yet another
> config file. I would like to see a section in the bazaar.conf file instead.

That is certainly another option that I thought would be an acceptable
way to store the user's list.  One reason that I had been thinking that a
separate file would be better was in thinking about setting up a default
list of "environment-ignore" rules for the user (as apposed to the
versioned project-ignore rules): with a separate file, it becomes easy to
create the file if it doesn't already exist, populating it with a default
list of environment-ignore rules (which the user can then feel free to
edit).  However, the idea of letting the user specify both additions and
subtractions to the default environment-ignore list would obviate the
need for this, and is a better solution.  This allows bzr to update its
list with newer editor swap/backup filenames, etc., and have those
changes be included for all users.

> Yes--I have the same feeling. That's why the new scheme is proposed to
> initialize the property value to the default and than only use that.

I think this is a good idea for the project-ignore rules (that ignore
generated files in the process of building the project), but that
environment-ignore rules should be a separate list that still has a
default that is not versioned with the project.  The reason for this is
that, while the build process for a project remains the same (and thus has
the same needs for ignoring generated files that it always had), the tools
that a user might use to edit files, and the alternative version-control
systems that the user might be playing with, etc., are in flux and change
with the times.

..wayne..