From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Katherine Cox-Buday <cox.katherine.e@gmail.com>
Cc: 41790@debbugs.gnu.org
Subject: [bug#41790] [PATCH] Update emacs-direnv
Date: Wed, 10 Jun 2020 20:05:12 +0200 [thread overview]
Message-ID: <87zh9alrtz.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87pna6zy3l.fsf@gmail.com> (Katherine Cox-Buday's message of "Wed, 10 Jun 2020 11:26:06 -0500")
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?
IIUC, they are to be used as a last resort, e.g., when the package
cannot possibly build without them.
Reason is propagated inputs pollute user's profile. E.g., someone may
want to use a different direnv, and this propagated input would conflict
with their package.
In this case, it is reasonable to expect users to install direnv
themselves.
> But! I am open to discussion.
I hear your arguments.
I'll let maintainers decide about this, and hopefully clarify what can
and cannot be propagated, at least in Emacs packages. This will be
useful feedback for future reviews.
Meanwhile, you can still provide a patch only bumping emacs-direnv. It
is also fine in you prefer to wait.
Regards,
next prev parent reply other threads:[~2020-06-10 18:06 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 [this message]
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
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=87zh9alrtz.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=41790@debbugs.gnu.org \
--cc=cox.katherine.e@gmail.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).