mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: musl@lists.openwall.com
Cc: enh <enh@google.com>, Aditya Kumar <appujee@google.com>
Subject: Re: [musl] fts.h
Date: Mon, 27 Jan 2025 11:17:04 -0800	[thread overview]
Message-ID: <CAMKF1srYQ3Abxtj6gni64eLnGW15OK77OwOePTQhdFJx--icfg@mail.gmail.com> (raw)
In-Reply-To: <20250127152534.GR10433@brightrain.aerifal.cx>

On Mon, Jan 27, 2025 at 7:25 AM Rich Felker <dalias@libc.org> wrote:
>
> On Thu, Jan 23, 2025 at 01:54:41PM -0500, enh wrote:
> > https://wiki.musl-libc.org/faq says "If glibc bug 15838 is fixed by
> > adding an fts64 interface in glibc, we could consider supporting it
> > with a matching ABI in musl, but it seems more likely that glibc will
> > just deprecate this interface", but that bug _was_ fixed in 2015 for
> > glibc 2.23...
>
> I wonder when that text was written. While we could certainly consider
> it, lack of any apparent need so far suggests that it wouldn't meet
> the modern criteria for inclusion in musl.
>
> The main motivation I could potentially see flipping this is if there
> are a significant number of programs shipping their own (e.g. gnulib?)
> versions of fts, that would save significant code-duplication disk
> space (or get better behavior of some sort) if using a shared copy in
> libc.

In yocto, we use the fts library https://github.com/pullmoll/musl-fts
and checked core layer and meta-openembedded layer which is 3000+ packages
following 8 are depending on it explicitly.
pmdk, fluentbit, libabigail, dracut, overlayfs-tools, libcgroup, ltp elfutils

>
> Rich

      parent reply	other threads:[~2025-01-27 19:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-23 18:54 enh
2025-01-24 23:20 ` [musl] fts.h appujee
2025-01-27 15:25 ` [musl] fts.h Rich Felker
2025-01-27 15:34   ` enh
2025-01-27 19:17   ` Khem Raj [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=CAMKF1srYQ3Abxtj6gni64eLnGW15OK77OwOePTQhdFJx--icfg@mail.gmail.com \
    --to=raj.khem@gmail.com \
    --cc=appujee@google.com \
    --cc=enh@google.com \
    --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).