On Tue, 5 Mar 2024 at 02:59, Greg Wooledge wrote:
We might *guess* that this change was made to make dash more strict
about POSIX minimalism (removing extensions), but without documentation
we can't do more than guess about motives.
The motivation is to avoid difference in behavior when compiled with
internal fnmatch implementation and with glibc
https://lore.kernel.org/dash/e341e41f-8c32-b6e4-8be3-8f94fae26...@gigawatt.nl/
Re: possible wrong behaviour with patterns using a quoted ^ at the start
of a bracket expression. Wed, 12 Jan 2022 17:20:54 +0000
This bug (you're right that it's a bug) is specific to builds that use
fnmatch(). In dash itself, ^ is always assumed as a literal. In builds
with --disable-fnmatch you get correct results.
On 05/03/2024 12:22, David wrote:
A bit more info:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028002
Unfortunately this bug has been left without a response from the
maintainer. The release notes mentions the issue:
https://www.debian.org/releases/bookworm/amd64/release-notes/ch-information.en.html#dash-circumflex
https://bugs.debian.org/1034344
