From: Andrew Cagney <andrew.cagney@gmail.com>
To: Rich Felker <dalias@libc.org>
Cc: musl@lists.openwall.com
Subject: Re: [musl] glob(GLOB_BRACE)
Date: Thu, 1 Feb 2024 10:53:27 -0500 [thread overview]
Message-ID: <CAJeAr6tN8seCZ5Hyfso_AgmkgCQ1Q5mMJ3uYUE_VQmU=GxTECg@mail.gmail.com> (raw)
In-Reply-To: <20240201142719.GV4163@brightrain.aerifal.cx>
On Thu, 1 Feb 2024 at 09:27, Rich Felker <dalias@libc.org> wrote:
>
> On Thu, Feb 01, 2024 at 08:48:01AM -0500, Andrew Cagney wrote:
> > FYI, It's on the BSDs and glibc.
> > Found by libreswan's test framework on alpine.
> For glob and GLOB_BRACE, it looks like it's "just" a matter of
> iterating over the different expansions and applying glob to each, but
> it seems to be underspecified how it interacts with escaping, special
> chars, slashes, etc.
>
> Do you have good reasons in favor of inclusion? My impression is that
> everything that wants/needs it is shipping its own version of GNU glob
> or whatever that has it, or else very little is using it; otherwise it
> would have come up before. But if adding it allowed a lot of things to
> drop GNU glob and just use the libc glob, that might be compelling.
for libreswan, after some digging:
2007 new code added with glob(GLOB_BRACE) call
2014 #ifdef GLOB_BRACE added; it turns out due to musl
2024 while merging some glob() calls; problem re-discovered
So libreswan took the path of least resistance. I suspect it wasn't alone.
Including it would let libreswan's config files be consistent across
platforms - no need for special documentation.
However, I also wonder if libreswan needs GLOB_BRACE. It isn't needed
to expand the recommended <<include /etc/ipsec.d/*.conf>>. I'll take
that up with libreswan.
prev parent reply other threads:[~2024-02-01 16:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 13:48 Andrew Cagney
2024-02-01 14:27 ` Rich Felker
2024-02-01 15:53 ` Andrew Cagney [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJeAr6tN8seCZ5Hyfso_AgmkgCQ1Q5mMJ3uYUE_VQmU=GxTECg@mail.gmail.com' \
--to=andrew.cagney@gmail.com \
--cc=dalias@libc.org \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).