From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Jonas Bernoulli <jonas@bernoul.li>
Cc: Philip Kaludercic <philipk@posteo.net>,
Okamsn <okamsn@protonmail.com>,
emacs-devel@gnu.org
Subject: Re: Adding the `prescient` packages to NonGNU ELPA?
Date: Wed, 23 Nov 2022 07:33:49 -0500 [thread overview]
Message-ID: <jwvr0xtvoqr.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <875yf6c7uo.fsf@bernoul.li> (Jonas Bernoulli's message of "Wed, 23 Nov 2022 10:56:15 +0100")
>> E.g. I can't see a clean way to install `git-commit` directly from its
>> VCS (i.e. recognized by `package-activate-all` and running from the Git
>> clone) without either forcing the install of `magit` at the same
>> time(&place) and/or having side-effects like sometimes shadowing another
>> installation of `magit`.
[...]
> This is an unusual, and in a sense extreme, example.
FWIW, I have no idea whether it's usual or not and what's its history.
> Prescient is a much more typical example,
I don't know in which way the situation is different for Prescient.
> git-commit/magit also has an unpleasant backstory. I can tell you about
> that in a private message. All I'll say here is that I did not actually
> want to add git-commit to magit but the behavior of its author forced me
> to accept the offer to take over as maintainer. At the time it seemed
> best to do that by adding it to the magit repository.
But that makes no difference to the problem at hand: by being in the
same directory as the other `magit` files, you can't add it to
`load-path` without adding those other files as well.
> On the other hand, I have some doubts this is actually going to benefit
> anyone. Is there anyone out there who does use git-commit but not magit?
This cuts both ways: if they're always installed in pair, why not keep
them as a single package?
Stefan
prev parent reply other threads:[~2022-11-23 12:33 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-20 3:27 Adding the `prescient` packages to NonGNU ELPA? Okamsn
2022-11-20 9:24 ` Philip Kaludercic
2022-11-20 11:23 ` Stefan Kangas
2022-11-20 15:19 ` Stefan Monnier
2022-11-20 15:41 ` Philip Kaludercic
2022-11-21 21:17 ` Richard Stallman
2022-11-22 13:53 ` Akib Azmain Turja
2022-11-23 23:12 ` okamsn
2022-11-26 0:50 ` Richard Stallman
2022-11-20 17:10 ` Visuwesh
2022-11-20 18:39 ` Stefan Monnier
2022-12-16 9:41 ` North Year
2022-12-16 19:25 ` Philip Kaludercic
2022-12-17 3:28 ` Stefan Monnier
2022-12-17 9:17 ` Philip Kaludercic
2022-12-17 15:52 ` Stefan Monnier
2022-12-17 16:07 ` Philip Kaludercic
2022-12-17 16:24 ` Philip Kaludercic
2022-12-17 18:01 ` Okamsn
2022-12-17 18:08 ` Philip Kaludercic
2022-12-17 18:39 ` Stefan Monnier
2022-12-20 1:32 ` Okamsn
2022-12-20 3:10 ` Stefan Monnier
2022-11-20 17:42 ` Okamsn
2022-12-05 0:27 ` Okamsn
2022-12-05 15:21 ` Stefan Monnier
2022-12-09 3:58 ` Okamsn
2022-12-09 15:08 ` Stefan Monnier
2022-12-09 15:27 ` Philip Kaludercic
2022-12-10 4:10 ` Richard Kim
2022-12-10 15:12 ` Stefan Monnier
2022-12-10 16:38 ` Richard Kim
2022-12-10 17:44 ` Stefan Monnier
2022-12-05 17:21 ` Philip Kaludercic
2022-12-16 2:04 ` Okamsn
2022-12-16 19:26 ` Philip Kaludercic
2022-11-22 15:41 ` Jonas Bernoulli
2022-11-22 21:09 ` Stefan Monnier
2022-11-23 9:56 ` Jonas Bernoulli
2022-11-23 12:33 ` Stefan Monnier [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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvr0xtvoqr.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=jonas@bernoul.li \
--cc=okamsn@protonmail.com \
--cc=philipk@posteo.net \
/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/emacs.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).