unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Ryan Prior via Guix-patches via <guix-patches@gnu.org>
Cc: "45284@debbugs.gnu.org" <45284-done@debbugs.gnu.org>
Subject: bug#45284: Double wrapper for protonvpn
Date: Thu, 24 Dec 2020 16:21:50 -0500	[thread overview]
Message-ID: <X+UGbiYD4L7ZWxXk@jasmine.lan> (raw)
In-Reply-To: <hi1hZzTSBsgxKsytOVex922VrDUMxlzSWf782iFOzJJ9rs8OEB_ZVC--I5dxg5-6nj7z3TWSCCwhOyaAfWkcP7Hy-4nl750gPjGVAXvFmBA=@protonmail.com>

On Wed, Dec 23, 2020 at 03:42:48AM +0000, Ryan Prior via Guix-patches via wrote:
> So what do you think? Is my dumb solution that works thus not dumb, and we should ship it? Or is there a better way of composing wrappers so that I'm not creating this billiards game situation with the entrypoint?

There are plenty of Guix packages that create multiple wrappers. I'm
sure there is room for improvement but this is fine if it works for you.




      reply	other threads:[~2020-12-24 21:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-17  4:53 [bug#45284] [PATCH] gnu: protonvpn-cli: Update to 2.2.6 Ryan Prior via Guix-patches via
2020-12-17  4:57 ` [bug#45284] Propagated packages Ryan Prior via Guix-patches via
2020-12-17  9:55   ` Efraim Flashner
2020-12-23  3:38 ` [bug#45284] [PATCH] gnu: protonvpn-cli: Stop propagating inputs Ryan Prior via Guix-patches via
2020-12-24 21:20   ` Leo Famulari
2020-12-23  3:42 ` [bug#45284] Double wrapper for protonvpn Ryan Prior via Guix-patches via
2020-12-24 21:21   ` Leo Famulari [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

  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=X+UGbiYD4L7ZWxXk@jasmine.lan \
    --to=leo@famulari.name \
    --cc=45284-done@debbugs.gnu.org \
    --cc=guix-patches@gnu.org \
    /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).