From: Katherine Cox-Buday <cox.katherine.e@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: 41790@debbugs.gnu.org
Subject: [bug#41790] [PATCH] Update emacs-direnv
Date: Wed, 10 Jun 2020 11:26:06 -0500 [thread overview]
Message-ID: <87pna6zy3l.fsf@gmail.com> (raw)
In-Reply-To: <871rmmoq7u.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Wed, 10 Jun 2020 18:11:49 +0200")
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
Thank you for the review!
> I understand that the Emacs library is not going to be useful if
> direnv is not available in user's profile. OTOH, installing this
> package from, e.g., M-x list-packages, wouldn't install direnv either.
The difference I see is that emacs's package manager is specifically for
emacs -- not for a user's system. Guix is a package manager for a user's
system which encompasses binaries and native libraries. This is one of
the reasons I prefer Guix packages to various language/tool package
managers because Guix can handle load paths and dependencies for me.
> Moreover, I assume anyone installing this Emacs package would have
> direnv available already.
I did not, nor did I know that I had to until it wasn't working and I
went and read the documentation.
> Considering the rule of thumb is to limit propagated inputs, I suggest
> to remove direnv.
I disagree. If propagated inputs are not for this -- making the package
even functional -- what are they for?
But! I am open to discussion.
--
Katherine
next prev parent reply other threads:[~2020-06-10 16:27 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 [this message]
2020-06-10 18:05 ` Nicolas Goaziou
2020-06-10 18:31 ` Katherine Cox-Buday
2020-06-10 18:46 ` Oleg Pykhalov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pna6zy3l.fsf@gmail.com \
--to=cox.katherine.e@gmail.com \
--cc=41790@debbugs.gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.