[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug#41790] [PATCH] Update emacs-direnv
From: |
Nicolas Goaziou |
Subject: |
[bug#41790] [PATCH] Update emacs-direnv |
Date: |
Wed, 10 Jun 2020 20:05:12 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) |
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,
- [bug#41790] [PATCH] Update emacs-direnv, Katherine Cox-Buday, 2020/06/10
- [bug#41790] [PATCH] Update emacs-direnv, Nicolas Goaziou, 2020/06/10
- [bug#41790] [PATCH] Update emacs-direnv, Katherine Cox-Buday, 2020/06/10
- [bug#41790] [PATCH] Update emacs-direnv, Oleg Pykhalov, 2020/06/10
- [bug#41790] [PATCH] Update emacs-direnv, Katherine Cox-Buday, 2020/06/11
- [bug#41790] [PATCH] Update emacs-direnv, Oleg Pykhalov, 2020/06/11
- [bug#41790] [PATCH] Update emacs-direnv, Oleg Pykhalov, 2020/06/11