v1.36

procrule release notes

v1.36

-u works again, as an alias for -8

v1.35 removed -u outright, so procrule -u exited with
procrule: invalid option -- u and every script, alias and job file carrying
it stopped. Both spellings are now accepted and mean exactly the same thing,
so a run written against either side of that change works.

-8 is still the spelling to use, and the reason is unchanged: mdxfind -8
selects the same engine there, because mdxfind -u already loads a userid
file and could never have carried this meaning. One letter, one meaning, in
both tools.

-u is kept rather than restored as the primary. procrule has no userid file,
so the letter is free and there is nothing for it to collide with — keeping it
costs nothing and breaking it cost everyone with a -u in a job file.

If you have been carrying a -u, nothing needs to change. If you are writing
something new, write -8.

Nothing else changed

The rule engines, the dispatch between them, discovery and the output format
are untouched. The whole source change is the option parse: one character in
each of the two getopt strings, a fall-through case label, and the help text.
A byte-mode run and a -8 run produce exactly what v1.35 produced.

Documentation

procrule(1) documents the alias inside the -8 entry, naming -8 as the
spelling to prefer and -u as kept for scripts written against v1.30 and
earlier. SYNOPSIS still shows -8 alone, deliberately. mdxfind(1) has
dropped its claim that procrule spells this switch -8: that was written
against procrule v1.30, where it was -u, and it told the reader to type
something the binary of the day rejected.