all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Vincent Legoll <vincent.legoll@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PACKAGE] musl libc
Date: Tue, 2 Aug 2016 22:18:13 +0200	[thread overview]
Message-ID: <CAEwRq=qX80B4bB_BPqPD6=vS8W_fuL75KxSG1au4d6tp4kXN6Q@mail.gmail.com> (raw)
In-Reply-To: <87shun46de.fsf@elephly.net>

> It’s fine to put it in a separate file “gnu/packages/musl.scm” and add
> it to the list of modules in “gnu/local.mk”.
>
> What follows is a short review with some comments.
>
>> (synopsis "New C standard library to power a new generation of
>> Linux-based devices")
>
> I would change it to just “Small C standard library”.  What do you
> think?

As you wish I just copied it from upstream web site...

>>     (description "The musl libc is lightweight, fast, simple, free, and strives
>> to be correct in the sense of standards-conformance and safety.")
>
> How about this instead?
>
>     “musl is a simple and lightweight C standard library.  It strives to
>      be correct in the sense of standards-conformance and safety.”
>
> “fast” is a bit of a loaded term, so we often avoid it.  Since all
> packages in Guix are “free” we usually drop this term from descriptions.

Ditto

>>     (home-page "http://www.musl-libc.org")
>>     (license (x11-style "file://COPYRIGHT"))))
>
> This looks good.  If you agree, I’ll copy the changes and make a commit
> with you as the author.
>
> Normally, contributors send changes as patches to the mailing list.  For
> future contributions it might be helpful to take a look at the
> “Contributing” section in the manual:

Yes, I just wanted feedback in order to make a real patch submission afterwards,
and thought it would be more readable as is, and I didn't know in
which file to put
it anyways... But if you want to do it, go ahead...

>     https://www.gnu.org/software/guix/manual/html_node/Contributing.html
>
> This essentially describes how to get started with Guix from a git
> clone, generate patches with “git format-patch” and how to send them via
> email.  If anything in there is confusing to you please let us know and
> we’ll try to help.

This is clear enough

>  You’re also welcome to visit the #guix IRC channel
> on Freenode for discussions or questions.

Yep, even if I'm not a big fan of irc, I already came to this channel
a few times

Thanks

-- 
Vincent Legoll

  reply	other threads:[~2016-08-02 20:18 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-30 12:19 [PACKAGE] musl libc Vincent Legoll
2016-08-02  8:45 ` ng0
2016-08-02 14:01 ` Ricardo Wurmus
2016-08-02 20:18   ` Vincent Legoll [this message]
2016-08-03 11:24     ` Ricardo Wurmus
2016-08-03 11:38       ` Vincent Legoll
2016-08-03 12:35         ` Ricardo Wurmus
2016-08-06 12:05           ` ng0
2016-08-08 13:26             ` Vincent Legoll
2016-10-06 21:08               ` ng0
2016-10-08 12:38                 ` David Craven
2016-10-08 13:54                   ` ng0
2016-10-08 14:53                     ` David Craven
2016-10-08 15:12                       ` ng0
  -- strict thread matches above, loose matches on Subject: below --
2016-08-03 13:25 David Craven
2016-08-12 19:15 ` Ricardo Wurmus
2016-08-13  9:32   ` Ricardo Wurmus
2016-08-13  9:44     ` Vincent Legoll
2016-08-13  9:55       ` David Craven
2016-08-13 10:00         ` Vincent Legoll
2016-08-13 10:17           ` David Craven
2016-08-14  7:46             ` Ricardo Wurmus
2016-08-08 16:47 David Craven
2016-08-08 18:43 ` Vincent Legoll
2016-08-08 18:46   ` David Craven

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='CAEwRq=qX80B4bB_BPqPD6=vS8W_fuL75KxSG1au4d6tp4kXN6Q@mail.gmail.com' \
    --to=vincent.legoll@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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.