unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Reily Siegel <mail@reilysiegel.com>
Cc: 50231@debbugs.gnu.org
Subject: [bug#50231] [PATCH] gnu: emacs-desktop-environment: Include runtime dependencies
Date: Tue, 07 Sep 2021 22:15:59 +0200	[thread overview]
Message-ID: <87a6ko9m68.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87k0jsfb2s.fsf@reilysiegel.com> (Reily Siegel's message of "Tue,  07 Sep 2021 15:19:07 -0400")

Hello,

Reily Siegel <mail@reilysiegel.com> writes:

> The emacs package can be configured to use other tools. However, unless
> the package is specifically configured otherwise, it will not work when
> installed. Without either these propagated inputs or special
> configuration, this package cannot perform any of its functions. 

I know, but this Emacs library is not supposed to provide the features
itself. I assume you use it on top of installed executables, as
explained in the package description:

  The package depends on the availability of shell commands to do the
  hard work for us.

Pulling all of them from an Emacs package sounds backward.

> Perhaps these could be included in a separate output?

Outputs are distinct part of the package output. Here, propagated
executables are not part of the Emacs library, so the suggestion does
not hold.

Maybe Guix is missing a "suggested depedencies" flag, somehow.

Anyhow, I think the status quo is fine. WDY (and others) T?

Regards,
-- 
Nicolas Goaziou




  reply	other threads:[~2021-09-07 20:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-27 18:36 [bug#50231] [PATCH] gnu: emacs-desktop-environment: Include runtime dependencies Reily Siegel
2021-09-06  9:17 ` Nicolas Goaziou
2021-09-07 19:19   ` Reily Siegel
2021-09-07 20:15     ` Nicolas Goaziou [this message]
2021-09-08  9:33       ` zimoun
2021-09-24 11:56       ` Ludovic Courtès

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=87a6ko9m68.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=50231@debbugs.gnu.org \
    --cc=mail@reilysiegel.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).