From: Maxime Devos <maximedevos@telenet.be>
To: "Konrad Hinsen" <konrad.hinsen@fastmail.net>,
zimoun <zimon.toutoune@gmail.com>,
"Ludovic Courtès" <ludo@gnu.org>
Cc: 57858-done@debbugs.gnu.org
Subject: [bug#57858] [PATCH] gnu: git-annex: Promote git to propagated input
Date: Mon, 17 Oct 2022 14:55:31 +0200 [thread overview]
Message-ID: <7affdc6d-6e67-aebd-df88-dd5d304c75d3@telenet.be> (raw)
In-Reply-To: <m1y1teep4h.fsf@fastmail.net>
[-- Attachment #1.1.1: Type: text/plain, Size: 833 bytes --]
On 17-10-2022 12:11, Konrad Hinsen wrote:
> But you are right in pointing out that this is an instance of a
> situation for which Guix should have a general policy. git-lfs is
> probably in exactly the same situation. Not emacs-magit though: it works
> perfectly fine without exposing git in the same profile. Being a git
> plugin is not the same as being a git wrapper.
The current policy, IMO, is that plugins don't propagate what they are
plugged into -- even if the plugin is useless without the thing it
plugs-in into (compare: search paths are set in 'consumers', not
'producers').
Taking 'emacs-magit' as an example, emacs-magit is an Emacs plugin, but
it doesn't propagate emacs.
Likewise, (in some usages) 'git-annex' is a git plugin, yet it (IMO)
shouldn't propagate git.
Greetings
Maxime.
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
prev parent reply other threads:[~2022-10-17 12:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 12:37 [bug#57858] [PATCH] gnu: git-annex: Promote git to propagated input Konrad Hinsen
2022-09-16 15:02 ` Maxime Devos
2022-09-17 9:56 ` Konrad Hinsen
2022-10-17 8:07 ` bug#57858: " Ludovic Courtès
2022-10-17 9:29 ` [bug#57858] " zimoun
2022-10-17 10:11 ` Konrad Hinsen
2022-10-17 11:02 ` zimoun
2022-10-17 12:55 ` Maxime Devos [this message]
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=7affdc6d-6e67-aebd-df88-dd5d304c75d3@telenet.be \
--to=maximedevos@telenet.be \
--cc=57858-done@debbugs.gnu.org \
--cc=konrad.hinsen@fastmail.net \
--cc=ludo@gnu.org \
--cc=zimon.toutoune@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 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.