[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: DEP-5: Files field and filename patterns



On Thu, Aug 26, 2010 at 04:59:24PM +0200, gregor herrmann wrote:
On Thu, 26 Aug 2010 08:39:54 +0900, Charles Plessy wrote:

> * Are find -name/-path globs a better idea than .gitignore?
> * Are shell-style globs the right idea? Should we use Perl regular
> expressions on the entire pathname instead?

I think that we can, and should, keep the rest of the syntax simple by using only the shell wildcards ‘?’ and ‘*’. I have not worked on any package where a more complex syntax would be needed.

I agree that shell globs are probably the easiest way both to write
(without checking pattern rules) and test (with a simple `ls'). [0]

Agreed.

Even the [] syntax (currently allowed - and also in gitignore syntax) I have not really found beneficial and wouldn't mind dropping, to keep syntax simple.


When I look at gitignore(5) I find in the example:

 # ignore objects and archives, anywhere in the tree.
 *.[oa]

I don't think the "anywhere in the tree" part is desirable for
debian/copyright.

That's the "find -path" variant, I believe. I use this for e.g. Makefile.in files.



I've fact I've written shell-style patterns free-handedly so far and
hoped that they would also be valid for `find' :)

Did you actually test your expressions with "find -path"?

I discovered at some point that all entries need a trailing ./ - e.g. debian/control is not valid - it needs to be expressed ./debian/control


 - Jonas

--
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

Attachment: signature.asc
Description: Digital signature


Reply to: