mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Isaac Dunham <idunham@lavabit.com>
To: musl@lists.openwall.com
Subject: Re: musl vs. Debian policy
Date: Thu, 7 Mar 2013 16:04:17 -0800	[thread overview]
Message-ID: <20130307160417.86e9d017.idunham@lavabit.com> (raw)
In-Reply-To: <CAK4o1WyQ3g3Txvpht0HHQv1shOw0259L-Drk788U4RFjEsbs_g@mail.gmail.com>

On Thu, 7 Mar 2013 18:56:35 +0000
Justin Cormack <justin@specialbusservice.com> wrote:

> 
> What is the idea of packaging Musl for Debian? I can see several options
> but none of them seem very plausible. No other package is likely to require
> Musl. A Musl based Debian might be nice but that's a very different
> requirement. Maybe I am missing something.

Mainly the same reason they include klibc, dietlibc, and uclibc-source: a small libc for initrds, small static binaries, and cross-compilation.
mksh, ngetty, and slidentd all refer to use of dietlibc, and klibc is used for initrds. 

musl's policy about maintaining ABI and availability as a shared library may prove advantageous to Debian, also.  

Up till now I've been speaking about reasons a musl package would be useful within a libc6-based distro; but a musl package is necessary for a Debian musl port. A good number of embedded systems start off Debian, Emdebian, or the uclibc port of Debian. The ability to build a Debian system based around musl may aid in adoption of musl, and Debian's attitude towards compatability makes it a good place to start.

I should note that with multiarch, it actually would be possible to use a prepackaged musl for cross-compilation. 

HTH, 
Isaac Dunham <idunham@lavabit.com>



  reply	other threads:[~2013-03-08  0:04 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-06 23:29 Isaac Dunham
2013-03-07 13:04 ` Rich Felker
2013-03-07 18:17   ` Christian Neukirchen
2013-03-07 18:45     ` Kurt H Maier
2013-03-07 18:49       ` Daniel Cegiełka
2013-03-08  0:41     ` Rich Felker
2013-03-08 15:13       ` Christian Neukirchen
2013-03-09  1:27         ` Rich Felker
2013-03-09 20:08           ` Christian Neukirchen
2013-03-10  3:29             ` Rich Felker
2013-03-10  3:39               ` Rich Felker
2013-03-08  1:03   ` Isaac Dunham
2013-03-08  1:10     ` Rich Felker
2013-03-08  4:03       ` Isaac Dunham
2013-03-09  1:23         ` Rich Felker
2013-03-07 18:56 ` Justin Cormack
2013-03-08  0:04   ` Isaac Dunham [this message]
2013-03-07 22:30 ` Rob Landley
2013-03-08  0:22   ` Isaac Dunham
2013-03-08  1:09     ` Kurt H Maier

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=20130307160417.86e9d017.idunham@lavabit.com \
    --to=idunham@lavabit.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).