mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: Symbol versioning approximation trips on compat symbols
Date: Mon, 28 Jan 2019 18:47:18 -0500	[thread overview]
Message-ID: <20190128234718.GE23599@brightrain.aerifal.cx> (raw)
In-Reply-To: <c9d14b21-36fa-3197-92c0-115589cd4176@adelielinux.org>

On Mon, Jan 28, 2019 at 05:41:10PM -0600, A. Wilcox wrote:
> On 01/28/19 17:12, Zach van Rijn wrote:
> > The official community-based musl site is the Wiki [1];
> > this might be a more appropriate venue for what you're seeking,
> > and it already does exactly what you're seeking.
> > 
> > 
> > [1]: https://wiki.musl-libc.org/projects-using-musl.html
> 
> 
> That page is also a bit of a mess.  I would clean it up but I don't know
> if I have the time.
> 
> It'd be nice if it had a divide between "experimental" distros and
> "production" distros, that is ones that intended to be run on a
> workstation/server vs those that are intended to be poked and prodded
> and used for research.  Also, "last activity" would be nice, so you can
> tell what's maintained.
> 
> (It'd be cool for Adélie, and probably Alpine, if the list were
> alphabetised, too ;) - but I won't push it.)

I'm not opposed to either idea, but I'm not sure how we'd define the
experimental vs production distinction. Some dists, especially
source-based ones like Sabotage, lack the selection of packages users
might expect from a production desktop or server distro, but they can
still be very suitable for production use in embedded or in small or
"more traditional" servers without all kinds of modern bloat.

Maybe it would make sense to suggest a few comparable well-known
distros for each one ("Debian-like", "Gentoo-like", "Buildroot-like",
etc.)?

Rich


  reply	other threads:[~2019-01-28 23:47 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-21 17:57 Florian Weimer
2019-01-24  1:43 ` Rich Felker
2019-01-24  9:28   ` u-uy74
2019-01-24 10:11     ` Florian Weimer
2019-01-24 11:09   ` Szabolcs Nagy
2019-01-24 11:18     ` Florian Weimer
2019-01-27  4:04       ` Rich Felker
2019-01-27  9:36         ` u-uy74
2019-01-28  6:34           ` Florian Weimer
2019-01-28  9:17             ` Timo Teras
2019-01-28 11:33               ` Szabolcs Nagy
2019-01-28 12:40             ` Szabolcs Nagy
2019-01-28 13:08             ` (OT?) Re: [musl] " u-uy74
2019-01-28 15:22               ` Markus Wichmann
2019-01-28 15:34                 ` Rich Felker
2019-01-28 15:29               ` Rich Felker
2019-01-29 17:13                 ` u-uy74
2019-01-30 14:57                   ` Rich Felker
2019-01-28 21:57             ` A. Wilcox
2019-01-28 22:52               ` Matias Fonzo
2019-01-28 23:12                 ` Zach van Rijn
2019-01-28 23:41                   ` A. Wilcox
2019-01-28 23:47                     ` Rich Felker [this message]
2019-01-29  3:22                       ` A. Wilcox
2019-01-29 19:40                         ` Matias Fonzo
2019-01-29 19:31                   ` Matias Fonzo

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=20190128234718.GE23599@brightrain.aerifal.cx \
    --to=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).