find: Allow '/' to be used with -perm for GNU compatibility

[ricardobranco777]

Since 2005 GNU find(1) no longer allows '+' to be used with -perm, forcing the use of a / instead.

This PR adds support for this character as synonym for '+'.

Fixes https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276326

[igalic]

I feel like this would require a documentation update

[ricardobranco777]

I feel like this would require a documentation update

Fixed.

[bsdimp]

Can you rebase to a newer main and do a git push --force-with-lease so that the style checker also runs.

To my eyeballs, though, this looks good.

[ricardobranco777]

--force-with-lease

Done.

[igalic]

one final request
looks fine otherwise

[igalic]

this file will need a .Dd bump

[ricardobranco777]

Fixed. Thanks!

[qemu-bsd-user]

Once the .Dd bump happens, I'll commit. It all looks good otherwise.
I also need to look at why my style checker didn't run with the forced push, but that's not the fault of the submitter...

[ricardobranco777]

Once the .Dd bump happens, I'll commit. It all looks good otherwise. I also need to look at why my style checker didn't run with the forced push, but that's not the fault of the submitter...

Fixed.

[jlduran]

I also need to look at why my style checker didn't run with the forced push

@bsdimp disguised as @qemu-bsd-user, maybe it is missing the synchronize activity type?
Ref: https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#pull_request, yes it is the only activity type not in the past tense.

[emaste]

I find preceded by a plus (“+”) or a slash (“/”) (for GNU compatibility), slightly awkward (although this entire -perm paragraph is already awkward).

I think / is not accepted by find on other BSDs or macOS, so we likely still prefer +? If the intent is to allow / for GNU compatibility but we feel that + is preferred I would probably leave the existing text intact, but add a sentence at the end along the lines of For compatibility with GNU find a slash ("/") is also accepted in place of a plus ("+").

In any case the code change LGTM (and thanks for improving GNU compatibility).

[bsdimp]

I find preceded by a plus (“+”) or a slash (“/”) (for GNU compatibility), slightly awkward (although this entire -perm paragraph is already awkward).

I think / is not accepted by find on other BSDs or macOS, so we likely still prefer +? If the intent is to allow / for GNU compatibility but we feel that + is preferred I would probably leave the existing text intact, but add a sentence at the end along the lines of For compatibility with GNU find a slash ("/") is also accepted in place of a plus ("+").

In any case the code change LGTM (and thanks for improving GNU compatibility).

Checking into things a bit more, POSIX.1 2001 (issue 6) and POSIX.1 2018 (issue 7) has the '+' sign listed, but not the '/' sign, so that's a gnu find extension. Gnu find evidentally deprecated + in favor of / in 2005. I've not checked to see if POSIX.1 202x has this or not. My not-completley-public standards archive is offline, so I can't check.

[bsdimp]

Merged. I hope it's OK, but I added a blurb in the STANDARDS section about this extension.