all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Jesse Gibbons <jgibbons2357@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: We reached 10.000 package
Date: Mon, 15 Jul 2019 14:37:05 +0200	[thread overview]
Message-ID: <87zhlfmq32.fsf@gnu.org> (raw)
In-Reply-To: <20190714210923.4312bf43@gmail.com> (Jesse Gibbons's message of "Sun, 14 Jul 2019 21:09:23 -0600")

Hello Guix!

Jesse Gibbons <jgibbons2357@gmail.com> skribis:

> On Sun, 14 Jul 2019 23:21:37 +0200
> Hartmut Goebel <h.goebel@crazy-compilers.com> wrote:
>
>> Hurrah!
>> 
>> GNU Guix now provides 10,026 packages (updated July 12, 2019).
>> 
>> Congratulations!
>> 
>> And many thanks to everybody who contributed to this great project!
>> 
>
> This is big news for Guix. Very much worth a small slice of banana
> bread in celebration.

Yay, congrats everyone!  \o/

> Yet there is still a lot to do. How many of these packages work as
> intended? Some of them have an error when guix builds them, some of
> them immediately crash, and some of them take so long to build that it
> is impractical to try to install them with guix.
>
> If you show me a list of packages that don't build correctly or
> immediately crash on startup, I will work on fixing them. I have no
> doubt some volunteers are willing to do the same. If I had access to a
> good server I would be willing to work on packages that take more than
> a day to build like guile-emacs.

There are both build errors and packaging issues reported at
<https://issues.guix.gnu.org>, so you won’t run out of ideas of packages
to work on.

If you do (!), you can also look at failing builds at
<https://ci.guix.gnu.org/jobset/guix-master>.

:-)

Thanks,
Ludo’.

      reply	other threads:[~2019-07-15 12:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-14 21:21 We reached 10.000 package Hartmut Goebel
2019-07-15  3:09 ` Jesse Gibbons
2019-07-15 12:37   ` Ludovic Courtès [this message]

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=87zhlfmq32.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=jgibbons2357@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.