From: Oleg Pykhalov <go.wigust@gmail.com>
To: Katherine Cox-Buday <cox.katherine.e@gmail.com>
Cc: 41790@debbugs.gnu.org, Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: [bug#41790] [PATCH] Update emacs-direnv
Date: Wed, 10 Jun 2020 21:46:19 +0300 [thread overview]
Message-ID: <87k10e92tg.fsf@gmail.com> (raw)
In-Reply-To: <87pna6zy3l.fsf@gmail.com> (Katherine Cox-Buday's message of "Wed, 10 Jun 2020 11:26:06 -0500")
[-- Attachment #1: Type: text/plain, Size: 868 bytes --]
Hi.
Katherine Cox-Buday <cox.katherine.e@gmail.com> writes:
[…]
> I disagree. If propagated inputs are not for this -- making the package
> even functional -- what are they for?
>
> But! I am open to discussion.
Propagated inputs could lead to conflicts in a Guix profile. The
simplest example I could remember is - you want upgrade package ‘A’
which propagates ‘direnv’, but you cannot because package ‘B’ propagates
it too. In this case you need to upgrade both ‘A’ and ‘B’ or delete ‘A’
(or ‘B’).
Instead we could make the package functional by substituting in
/gnu/store/…-emacs-direnv-…-checkout/direnv.el file ‘direnv--detect’
("Detect the direnv executable.") procedure which could return a path to
‘direnv’ binary as a string directly without calling ‘executable-find’.
WDYT?
Oleg.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2020-06-10 18:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 15:12 [bug#41790] [PATCH] Update emacs-direnv Katherine Cox-Buday
2020-06-10 16:11 ` Nicolas Goaziou
2020-06-10 16:26 ` Katherine Cox-Buday
2020-06-10 18:05 ` Nicolas Goaziou
2020-06-10 18:31 ` Katherine Cox-Buday
2020-06-10 18:46 ` Oleg Pykhalov [this message]
2020-06-11 14:44 ` Katherine Cox-Buday
2020-06-11 20:03 ` Oleg Pykhalov
2020-06-11 20:31 ` Oleg Pykhalov
2021-08-06 4:49 ` bug#41790: " Maxim Cournoyer
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=87k10e92tg.fsf@gmail.com \
--to=go.wigust@gmail.com \
--cc=41790@debbugs.gnu.org \
--cc=cox.katherine.e@gmail.com \
--cc=mail@nicolasgoaziou.fr \
/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).