unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Raghav Gururajan via Guix-patches via <guix-patches@gnu.org>
To: Leo Prikler <leo.prikler@student.tugraz.at>, 48326@debbugs.gnu.org
Subject: [bug#48326] [PATCH v4] gnu: Add remmina.
Date: Tue, 11 May 2021 11:37:07 -0400	[thread overview]
Message-ID: <67629c5f-45ca-e700-ec02-1d9422256acc@raghavgururajan.name> (raw)
In-Reply-To: <25a72e63e9807e531756e80952360f67260b4e80.camel@student.tugraz.at>


[-- Attachment #1.1: Type: text/plain, Size: 1039 bytes --]

Hi Leo,

> I don't think an extra file is needed here.  Remmina can fit quite well
> to the other VNC clients.

True. But adding it in rdesktop.scm or vnc.scm causes cyclic-dependency, 
when I add #:use-module (gnu packages vnc) or #:use-module (gnu packages 
rdesktop); respectively.

> Adjust how? > You already have remmina.scm in your ChangeLog.

Corrected them in v5.

> I don't think this does, what you think it does.
> "REMMINA_PLUGIN_PATH" is here interpreted as a single directory; usage
> as a PATH variable is therefore dangerous.  (Consider a setting, where
> REMINA_PLUGIN_PATH="guix-profile-a/...:guix-profile-b/...")
> 
> Also consider packages like Emacs, where the inclusion of their own
> outputs in their path variables was dangerous.  (Although in this case,
> it's probably sane, since you're using an extra output, but do verify
> Remmina to work as intended without it.)

Thanks for the pointers. I tried running remmina without installing its 
other output, no hiccups.

Regards,
RG.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

  reply	other threads:[~2021-05-11 15:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-10  3:05 [bug#48326] [PATCH 0/0]: Add remmina Raghav Gururajan via Guix-patches via
2021-05-10  3:10 ` [bug#48326] [PATCH v1] gnu: " Raghav Gururajan via Guix-patches via
2021-05-10 15:06 ` [bug#48326] [PATCH v2] " Raghav Gururajan via Guix-patches via
2021-05-10 17:01 ` [bug#48326] [PATCH v3] " Raghav Gururajan via Guix-patches via
2021-05-10 23:33 ` [bug#48326] [PATCH v4] " Raghav Gururajan via Guix-patches via
2021-05-11  6:02   ` Leo Prikler
2021-05-11 15:37     ` Raghav Gururajan via Guix-patches via [this message]
2021-05-11 15:29 ` [bug#48326] [PATCH v5] " Raghav Gururajan via Guix-patches via
2021-05-11 16:12 ` [bug#48326] [PATCH v6] " Raghav Gururajan via Guix-patches via
2021-05-11 18:04 ` [bug#48326] [PATCH v7] " Raghav Gururajan via Guix-patches via
2021-05-11 19:54 ` [bug#48326] [PATCH v8] " Raghav Gururajan via Guix-patches via
2021-05-11 20:04 ` [bug#48326] [PATCH v9] " Raghav Gururajan via Guix-patches via
2021-05-11 22:33 ` bug#48326: (no subject) Raghav Gururajan via Guix-patches via

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=67629c5f-45ca-e700-ec02-1d9422256acc@raghavgururajan.name \
    --to=guix-patches@gnu.org \
    --cc=48326@debbugs.gnu.org \
    --cc=leo.prikler@student.tugraz.at \
    --cc=rg@raghavgururajan.name \
    /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).