mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "Laurent Bercot" <ska-dietlibc@skarnet.org>
To: musl@lists.openwall.com
Subject: Re: [musl] option to enable eh_frame
Date: Sat, 17 Jul 2021 07:24:40 +0000	[thread overview]
Message-ID: <emee691b46-779e-42e2-92d1-969c1f32f5b4@elzian> (raw)
In-Reply-To: <33b6a644-4930-98e5-6376-504867b6423a@dereferenced.org>


>It is about debugging, but specifically enabling downstream users to do basic debugging without having to install the musl-dbg package.  This is commonly requested both in public Alpine channels, and also in various support engagements Alpine developers have with their customers in a personal capacity.  It has been a point of contention for many years in the Alpine community, as a result.

  From what I can see, this point of contention has not exactly stopped
Alpine's expansion.

  Using Alpine comes with benefits; it also comes with some drawbacks,
and every reasonable user should be able to understand this. As a
maintainer, it obviously makes sense to try and minimize these 
drawbacks,
but are we really talking about a situation where the user's complaint
is 'I have to type "apk add musl-dbg" before performing debugging' ?

  Are we really talking about a situation where the proposed solution
to that complaint is *forking the libc that is a huge part of Alpine's
success in the first place* ?

  I suspect there is a lot being left unsaid here, because at face value,
the cost-benefit analysis is obvious and I don't understand how this is
even a question.

  Without any more information, what it looks like to me is corporate
lobbying, which Alpine has always managed to deal with in a reasonable
manner in the past and I am not sure what changed.

--
  Laurent


  parent reply	other threads:[~2021-07-17  7:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-16  9:16 Timo Teras
2021-07-16 15:57 ` Rich Felker
2021-07-16 22:06   ` Ariadne Conill
2021-07-17  0:41     ` Rich Felker
2021-07-17  1:08       ` Ariadne Conill
2021-07-17  1:10         ` Érico Nogueira
2021-07-17  7:24         ` Laurent Bercot [this message]
2021-07-18  8:16       ` Timo Teras
2021-07-17  7:33   ` Timo Teras
2021-07-17 10:38     ` Timo Teras
2021-07-17 13:25     ` Rich Felker
2021-07-17 15:40       ` Timo Teras
2021-07-17 16:09         ` Rich Felker
2021-07-17 19:52           ` Ariadne Conill
2021-07-17 23:56             ` Rich Felker
2021-07-18  1:40               ` Ariadne Conill
2021-07-18  2:23                 ` Ariadne Conill
2021-07-18  6:09               ` Timo Teras
2021-07-18  7:20                 ` Timo Teras
2021-07-24 23:45                   ` Fangrui Song
2022-04-17 19:50     ` Fangrui Song

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=emee691b46-779e-42e2-92d1-969c1f32f5b4@elzian \
    --to=ska-dietlibc@skarnet.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).