plans for 0.9: default ignores

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Martin Pool wrote:
> On 11 Jul 2006, William Dode <wilk-ml at flibuste.net> wrote:
>> Hi,
>>
>> I don't have any problem to update .bzrignore for my old project, i use
>> to look at the status and see imediatly that i need to do it.
>>
>> But for new project, what is the best way to automaticaly add his own
>> .bzrignore on each init ? A plugin ? maybe this plugin could also
>> upgrade old .bzrignore ?
> 
> I think if we take care of editor backups and similar things with a
> global ignore with reasonable defaults then the ignore lists will
> largely depend on the particular project, so an automatic setup may have
> limited use.  

I've thought about it some more. And it does seem like we have a
reasonable use case. Editor files should go in ~/.bazaar/ignore, but
*.o, and *.py[co] should go in .bzrignore. I think it would be
reasonable to just do a short obvious list into .bzrignore, which people
can prune whenever they feel like.

I know we want our 'bzr init; bzr add; bzr commit' time to be super fast
even on a kernel sized tree. But I think if we can make it 'pretty
fast', and people can tweak it slightly with:

'bzr init; :>.bzrignore; bzr add; bzr commit'

That may be reasonable. Because it helps the other 90+% of people who
just want to get going with a new project.

> 
> You get into needing to define particular project styles or templates,
> which would be good for a plugin but not so good for the core.

I do agree that ultimately you want templates, but it might be
reasonable to have the short list automatically generated.

> 
> I think a plugin would be appropriate.  We should add a post-init hook
> that plugins can link into.
> 

I think having a short-list that is automatically put in .bzrignore,
which might even be empty, and then plugins can add new entries to it.

By the way, I still haven't gotten any feedback for my other ignore changes.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEt7ljJdeBCYSNAAMRAtKLAKCQcxIxuvqwT7lI8/EW+h6LILgrkQCbBewY
Ow0pHX7eNtIL8SkWBRemE18=
=Bz6O
-----END PGP SIGNATURE-----