mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "gs@int3.at" <gs@int3.at>
To: musl@lists.openwall.com
Cc: Rich Felker <dalias@aerifal.cx>
Subject: Re: Call for musl-based distro blurbs
Date: Thu, 07 Jun 2012 15:55:34 +0200	[thread overview]
Message-ID: <4FD0B2D6.5080209@int3.at> (raw)
In-Reply-To: <20120525232222.GA30663@brightrain.aerifal.cx>

On 05/26/2012 01:22 AM, Rich Felker wrote:
> Hi all,
> I'm planning to overhaul the musl website soon, and I'd like to
> include information on all distros/projects using musl. This will
> serve both to demonstrate musl's completeness and get some attention
> for projects based on musl. Supposedly everyone in #musl has a distro,
> so by now that should be quite a lot... ;-)
>
> Some things that would be good to include in a description of your
> projects would be the basic idea, what makes it unique, what new
> concepts/features/tools it's based on (e.g. package manager or build
> automation), the number of packages included or successfully built on
> it, etc.
>
> No definite ETA yet but I'll probably get the new website up somewhere
> between 0.9.1 and 0.9.2, assuming 0.9.1 doesn't run into any nasty
> release issues that require a quick 0.9.2 to replace it...
>
> Rich
>
here's the blob for https://github.com/rofl0r/sabotage

"this sabotage fork aims to stay up to date, and keep the core base 
system (busybox, development tools) statically compiled. it uses a 
hardened kernel and has experimental Xfbdev support. the package manager 
was written from scratch in C and aims to provide a parallel build 
experience. there are a couple of tweaks applied to make the whole 
system build in less than 40 minutes on a 8-core machine. the package 
manager allows to customize the build process using templates (possible 
use cases: automatic binary package generation, usage of a custom 
prefix...)"

--JS


  parent reply	other threads:[~2012-06-07 13:55 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-25 23:22 Rich Felker
2012-05-26  5:00 ` Kyle Sanderson
2012-05-26  5:06   ` Szabolcs Nagy
2012-06-07 13:55 ` gs [this message]
2012-06-07 14:08   ` Szabolcs Nagy
2012-06-07 15:00     ` gs
2012-06-07 14:49       ` Rich Felker
2012-06-07 15:40         ` Christian Neukirchen
2012-06-07 15:47           ` Rich Felker
2012-06-07 16:12             ` gs
2012-06-07 16:05               ` Jeremy Huntwork
2012-06-07 16:11                 ` aep
2012-06-07 16:17                 ` Daniel Cegiełka
2012-06-07 16:16                   ` Rich Felker
2012-06-07 16:38                     ` Daniel Cegiełka
2012-06-07 16:37                       ` Rich Felker
2012-06-07 17:06                         ` Luca Barbato
2012-06-07 17:19                           ` Daniel Cegiełka
2012-06-07 17:39                           ` Christian Neukirchen
2012-06-07 17:49                             ` Szabolcs Nagy
2012-06-08  2:06 ` Ivan Kanakarakis
2012-06-08 12:51   ` Szabolcs Nagy

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=4FD0B2D6.5080209@int3.at \
    --to=gs@int3.at \
    --cc=dalias@aerifal.cx \
    --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).