unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Sree Harsha Totakura <sreeharsha@totakura.in>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 2/2] gnu: gnunet: Add gnunet-0.10.0.
Date: Thu, 30 Jan 2014 22:11:10 +0100	[thread overview]
Message-ID: <87ha8lb2fl.fsf@gnu.org> (raw)
In-Reply-To: <1391099831-14896-2-git-send-email-sreeharsha@totakura.in> (Sree Harsha Totakura's message of "Thu, 30 Jan 2014 17:37:11 +0100")

Sree Harsha Totakura <sreeharsha@totakura.in> skribis:

> * gnunet/packages/gnunet.scm (gnunet): New variable.  Thanks to Zerwas for the initial recipe.
> * gnu/package/patches/gnunet-fix-scheduler.patch: Patch to fix bug in Gnunet's scheduler.
> * gnu/package/patches/gnunet-fix-tests.patch: Patch to fix bugs in testcases and to disable testscases which rely on name resolution.
> * gnu-system.am (dist_patch_DATA): Add the above two patch files.

Excellent!

Can you wrap lines to ~75 chars?  Also, you can use ‘Co-authored-by:
Zerwas’ if deemed appropriate here.

s/Gnunet/GNUnet/

The .patch files above should just have “New files” in the commit log
(see other commits for examples.)  However, can you please move the
description of what the patches do at the top of the patches themselves,
possibly with a reference to the upstream commit/bug report/discussion?

> +   (arguments
> +    '(#:phases
> +      (let* ((check (assq 'check %standard-phases))
> +             (alist (delete check %standard-phases))
> +             (testsetup
> +              (lambda* (#:key outputs #:allow-other-keys)
> +                (let ((out (assoc-ref outputs "out")))
> +                  (setenv "GNUNET_PREFIX" out)
> +                  (setenv "PATH" (string-append (getenv "PATH") ":" out "/bin"))
> +                  #t))))
> +        (display %standard-phases)
> +        (alist-cons-after 'testsetup (car check) (cdr check)
> +                          (alist-cons-after 'install 'testsetup testsetup
> +                                            alist)))))

I think the ‘display’ is a leftover, right?  ;-)

I would rather write it this way:

  (let* ((check (assq-ref %standard-phases 'check))
         (pre-check
           (lambda* ...)))
    (alist-cons-after 'pre-check 'check check
                      (alist-cons-after 'install 'pre-check pre-check
                                        (alist-delete 'check
                                                       %standard-phases))))

(Woow, this ought to be simpler...)

> +   (synopsis "Secure P2P networking framework with cool applications")
> +   (description
> +    "GNUnet is a framework for secure peer-to-peer networking that does not
> +use any centralized or otherwise trusted services. Our high-level goal is to
> +provide a strong free software foundation for a global network that provides
> +security and in particular respects privacy.  GNUnet started with an idea for
> +anonymous censorship-resistant file-sharing, but has grown to incorporate
> +other applications as well as many generic building blocks for secure
> +networking applications. In particular, GNUnet now includes the GNU Name
> +System, a privacy-preserving, decentralized public key infrastructure")

Could you run ‘make sync-descriptions’ and use whatever synopsis and
description it suggests?  (That comes from the canonical GNU package
database.)

Thanks for the nice work!

Ludo’.

  reply	other threads:[~2014-01-30 21:16 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-30 16:36 Gnunet-0.10.0 recipe Sree Harsha Totakura
2014-01-30 16:37 ` [PATCH 1/2] gnu: gnunet: Remove Gstreamer dependency Sree Harsha Totakura
2014-01-30 16:37   ` [PATCH 2/2] gnu: gnunet: Add gnunet-0.10.0 Sree Harsha Totakura
2014-01-30 21:11     ` Ludovic Courtès [this message]
2014-01-30 22:41       ` [PATCH] gnu: gnunet: Add GNUnet-0.10.0 Sree Harsha Totakura
2014-02-10 22:04   ` [PATCH 1/2] gnu: gnunet: Remove Gstreamer dependency Ludovic Courtès
2014-01-30 22:39 ` Gnunet-0.10.0 recipe Andreas Enge
2014-01-30 22:56   ` Sree Harsha Totakura
2014-01-30 23:33     ` Sree Harsha Totakura
2014-01-30 23:33       ` [PATCH] gnu: gnunet: Add GNUnet-0.10.0 Sree Harsha Totakura
2014-01-31 16:17         ` Mark H Weaver
2014-02-02 18:28           ` Ludovic Courtès
2014-02-10 22:15         ` Ludovic Courtès
2014-02-10 22:33           ` Andreas Enge
2014-02-11  8:05             ` Ludovic Courtès
2014-02-11  8:25               ` Andreas Enge
2014-02-11 14:11                 ` Andreas Enge
2014-02-11 10:05             ` Sree Harsha Totakura
2014-02-11 10:10               ` Andreas Enge
2014-02-11 10:47                 ` Ludovic Courtès
2014-02-11 18:17               ` [PATCH] gnu: curl, gnurl: Fix failing testcase 172 Sree Harsha Totakura
2014-02-11 19:00                 ` Andreas Enge
2014-01-31  8:54       ` Gnunet-0.10.0 recipe Andreas Enge
2014-02-03 22:17         ` Andreas Enge
2014-02-03 23:00           ` Ludovic Courtès
2014-02-05 17:27             ` Andreas Enge
2014-02-11 20:49               ` Andreas Enge
2014-02-11 22:17                 ` Sree Harsha Totakura
2014-02-12 15:15                   ` (unknown), Sree Harsha Totakura
2014-02-12 15:15                     ` [PATCH] gnu: gnunet: Fix failing testcases Sree Harsha Totakura
2014-02-12 17:37                       ` Ludovic Courtès
2014-02-12 17:36                     ` none Ludovic Courtès
2014-02-12 17:38                       ` none Sree Harsha Totakura
2014-02-12 19:25                       ` none Andreas Enge
2014-02-12 20:30                         ` none Ludovic Courtès
2014-02-12 20:53                           ` none Andreas Enge
2014-02-04  0:18           ` Gnunet-0.10.0 recipe Sree Harsha Totakura
2014-01-31 16:05     ` Ludovic Courtès
2014-02-03 22:19       ` Andreas Enge
2014-02-03 22:57         ` Ludovic Courtès
2014-02-04  0:21           ` Sree Harsha Totakura
2014-02-04  8:06             ` Christian Grothoff

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ha8lb2fl.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=sreeharsha@totakura.in \
    /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.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).