all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Andre Batista <nandre@riseup.net>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] Add Tor client only package definition
Date: Sun, 24 May 2020 22:51:16 +0200	[thread overview]
Message-ID: <87y2phys3f.fsf@gnu.org> (raw)
In-Reply-To: <20200517031127.GA17209@andel> (Andre Batista's message of "Sun,  17 May 2020 00:11:27 -0300")

Hi Andre,

Andre Batista <nandre@riseup.net> skribis:

> Starting on version 0.4.3.5, Tor provides a configuration flag to
> disable relay code (--disable-module-relay). Considering most
> people are running clients, not relays, I thought it would be
> nice for guix to have a client-only package definition (maybe
> it could even be the default?). What do you think?

What difference does it make, for instance in terms of the total size
returned by “guix size tor-client” vs. “guix size tor”?

Are there other considerations, such as a reduced attack surface?

> I've tested the code below and it works as expected on my guix
> install. However, since I'm neither a schemer nor guixpert, fell
> free to teach me how to do it the guix way.

It looks good to me overall!  Some nitpicking:

> + (define-public tor-client
> +   (package
> +     (inherit tor)
> +     (name "tor-client")
> +     (arguments
> +      `(#:configure-flags
> +        `(,@(cons "--disable-module-relay"
> +             ,(cadr (package-arguments tor))))))

We’d rather use ‘substitute-keyword-arguments’ to augment
#:configure-flags without touching the other keyword arguments (there
are several examples in the source).

> +     (synopsis "Client to the anonymous Tor network")
> +     (description
> +      (string-append (package-description tor)
> +       "\n\nThis package only provides the client funcionality to the Tor
> +Network.  If you want to setup a relay you need to install @code{tor}."))))

We generally avoid concatenating text like this, for the reasons
explained at:

  https://guix.gnu.org/manual/en/html_node/Synopses-and-Descriptions.html

Regarding the format of patches, you can take a look at this:

  https://guix.gnu.org/manual/en/html_node/Submitting-Patches.html

Thanks,
Ludo’.


  reply	other threads:[~2020-05-24 20:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-17  3:11 [PATCH] Add Tor client only package definition Andre Batista
2020-05-24 20:51 ` Ludovic Courtès [this message]
2020-05-26 14:56   ` Andre Batista
2020-05-31 19:40     ` André Batista
2020-05-31 23:42       ` Andre Batista
2020-06-03  4:49         ` Andre Batista
2020-06-16 22:59           ` André Batista
2020-07-02  9:36             ` Ludovic Courtès
2020-07-03 20:24               ` André Batista

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