Jim Klimov <jimklimov+...@gmail.com> writes:
> A solution similar to neighboring code posted as part of
> https://github.com/networkupstools/nut/pull/3042 - thanks again for raising
> this point.
>
> @Greg: can you please check that branch with pkgsrc et al?
Sure, will grab it and run it through build without pkgsrc, and then as pkgsrc.
> Regarding `\s` - good catch, as I read your post, I was sure it is used
> all over the place... but in fact only in perl code (also Java/groovy in CI
> libs), so not quite a GNU-only extension. Native Sun and BSD sed's were
> okay with that too. Most shell code went with "[ ${TABCHAR}]" where
> TABCHAR="`printf '\t'`" because indeed many sed's or especially grep's
> treat direct `\t` as escaped character "t". Missed doing that here. Once!
> And you got me on that! :D
Perl doesn't use POSIX Regular Expressions (BRE or ERE); it uses
Perl-Compatible Regular Expressions, which is yet a third language!
And, there isn't really at this point "BSD sed". There is a sed in each
release of each BSD, and they mostly have common ancestry, and often
improvements migrate. There's also likely "heirloom sed".
> Regarding commentary on docs, fair enough about the configure.ac
> script, but does at least `docs/configure.txt` explain it satisfactorily?
Didn't think to look there, but will have a look.
Not a bar to release as this is not new, just newly complained about!
_______________________________________________
Nut-upsdev mailing list
Nut-upsdev@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev
