all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ng0 <ng0@we.make.ritual.n0.is>
To: Vincent Legoll <vincent.legoll@gmail.com>,
	guix-devel <guix-devel@gnu.org>
Subject: Re: [PACKAGE] sinit
Date: Sat, 30 Jul 2016 22:49:28 +0000	[thread overview]
Message-ID: <87r3aa68sn.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <CAEwRq=rhE0pZ8_1LphqD1Tu=SWBygjKuF0FDLbSTPbx1k_uEJw@mail.gmail.com>

Vincent Legoll <vincent.legoll@gmail.com> writes:

> Hello,
>
> here is the packaging of sinit, a minimalistic /sbin/init replacement.
>
> It shows the use of the musl libc previously posted.
>
> Please advise on how to further proceed with the submission,
> where should I put this package, etc...
>
> Thanks

I'd like to test musl, but I would not know how to test sinit…
While I had this (musl) on my todo list as well, is sinit only limited
to musl? I guess it's not, but I don't know the software.


It would be best if the choice of libc was more dynamic.. uclibc-ng is
on my todo list for that. But I don't know how to approach this,
same goes for libressl v openssl situation.
Create lots of inheriting packages? Some packages require patches for
musl and libressl (outside of guix).

This is a bit affected by my experience in Gentoo where I dropped musl
only because I needed a "vanilla" environment for packaging (and feel
like not fixing musl problems in addition to maintaining packages).
-- 
♥Ⓐ  ng0
Current Keys: https://we.make.ritual.n0.is/ng0.txt
For non-prism friendly talk find me on http://www.psyced.org

  parent reply	other threads:[~2016-07-30 22:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-30 12:33 [PACKAGE] sinit Vincent Legoll
2016-07-30 13:46 ` Vincent Legoll
2016-07-30 16:19   ` Vincent Legoll
2016-08-07  0:48     ` Leo Famulari
2016-08-07 11:55       ` ng0
2016-08-08 12:48         ` Vincent Legoll
2016-08-09 18:42           ` Ricardo Wurmus
2016-07-30 22:49 ` ng0 [this message]
2016-08-02  7:00   ` Vincent Legoll

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=87r3aa68sn.fsf@we.make.ritual.n0.is \
    --to=ng0@we.make.ritual.n0.is \
    --cc=guix-devel@gnu.org \
    --cc=vincent.legoll@gmail.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.