From: Efraim Flashner <efraim@flashner.co.il>
To: Ryan Prior <rprior@protonmail.com>
Cc: "45284@debbugs.gnu.org" <45284@debbugs.gnu.org>
Subject: [bug#45284] Propagated packages
Date: Thu, 17 Dec 2020 11:55:45 +0200 [thread overview]
Message-ID: <X9srIWL1uGriQV8i@E5400> (raw)
In-Reply-To: <znN3w1zeQMxd5xDJYakJkcZcmV7DrAuIJeD6XuqJfmKn1kH7F3up0wZkR600r6i8R-lewTj1woXFuD2bZtdJqMsEAn8i7Wzaqe_W6phcHjo=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 899 bytes --]
On Thu, Dec 17, 2020 at 04:57:24AM +0000, Ryan Prior via Guix-patches via wrote:
> This protonvpn-cli package propagates a bunch of things, even moreso than before. I've verified that it needs them to connect, but I think we can avoid propagating them if I carefully go in and patch the system shell invocations to use explicit paths.
>
> I don't know when I'll have time to do that, so I'd recommend merging this patch to make the latest protonvpn-cli available. In any case I'll try and get a patched package with minimal if any propagation out ASAP.
>
Does the current protonvpn-cli not work? That is a lot of propagated
inputs. Is it possible to wrap the binary instead?
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-12-17 9:59 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 [this message]
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 ` bug#45284: " Leo Famulari
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=X9srIWL1uGriQV8i@E5400 \
--to=efraim@flashner.co.il \
--cc=45284@debbugs.gnu.org \
--cc=rprior@protonmail.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 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).