On Mon, Nov 19, 2007 at 11:43:13AM -0800, Joe Di Pol wrote:
> Currently it looks like filter values are limited to identifier syntax
> only. So
>
> arch = i386
>
> is valid, but
>
> arch = 386
>
> is not.
Ick. Using the python code parser there was convenient, but we need a real
lexer/parser. I've got an OSR open to integrate PLY; I should ping the
lawyer.
> Also the only comparison operator is "=".
Right.
> Are there any plans to enhance the capabilities of filters
> in the future? Like supporting numeric values and ">", "<",
> ">=", etc?
Well, there's something in doc/filter.txt, but I hadn't considered
comparisons as such, nor am I entirely sure what they'd be useful for. I
had thought of regular expression matching so that you could do something
like
mode =~ [^24][0-7][0-7][0-7]
to filter out set[ug]id files, and
path =~ usr/foo/blah.*
to filter entire swaths of the filesystem, however unsupported actually
doing so might be. :)
But none of that is remotely in stone; if we need new syntax for filters to
solve problems, there's nothing stopping us.
Danek
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
