* Marc Haber <[EMAIL PROTECTED]> [080522 15:52]:
> This is a surprise. The meaning of the comma is not explained, and the
> | is usually parsed as "or", which would make your explanation wrong.
> 
> Additionally, the requirement to put the value to be compared against
> in parenthesis ("Source (==blub)") is a very uncommon syntax which I
> have never seen outside Package Dependencies.

> > Any suggestions for a better text to describe those lines
> > highly welcome, I suck at writing documentation.
> 
> Unfortunately, I am far away from even understanding the bizarre
> syntax to even use it, let alone write documentation about it.

Ok, so here my next try:

| The format of the formulas is those of the  dependency
| lines in Debian packages with some extras.  That means
| a formula consists of names of fields with a  possible
| condition for its content in parentheses.  These atoms
| can be combined with an exclamation mark '!'  (meaning
| not),  an pipe symbol '|' (meaning or) and an coma ','
| (meaning and).  Additionally parentheses can  be  used
| to change binding.
|
| The  values  checked  are  directly the headers in the
| repspective index file compared alphabetically.   That
| means that each part Fieldname (cmp value) of the for-
| mula will be true for exactly those package that  have
| in  the  Package  or Sources file a line starting with
| fieldname and a value is alphabetically cmp to  value.
|
| Examples:
|
| reprepro  -b  .  listfilter test2 'Section (== admin)'
| will list all packags in distribtuion  test2  with  an
| Section field
|
| reprepro  -b  .  -T  deb  listfilter test2 'Source (==
| blub) | ( !Source , Package (== blub) )' will find all
| .deb  Packages  with either an Source field blub or no
| Source field and a Package field  blub.   (That  means
| all  package  generated  by  an  source  package blub,
| except those also specifying a version number with its
| Source).

Anything still missing?

Hochachtungsvoll,
        Bernhard R. Link
-- 
"Never contain programs so few bugs, as when no debugging tools are available!"
        Niklaus Wirth



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to