From: Philip Kaludercic <philipk@posteo.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Stefan Kangas <stefankangas@gmail.com>,
Okamsn <okamsn@protonmail.com>,
emacs-devel@gnu.org
Subject: Re: Adding the `prescient` packages to NonGNU ELPA?
Date: Sun, 20 Nov 2022 15:41:12 +0000 [thread overview]
Message-ID: <87wn7pljl3.fsf@posteo.net> (raw)
In-Reply-To: <jwvmt8l4pxm.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sun, 20 Nov 2022 10:19:41 -0500")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> Stefan Kangas [2022-11-20 03:23:09] wrote:
>> Philip Kaludercic <philipk@posteo.net> writes:
>>>> All of these packages live in the same repository in the link below.
>>>
>>> Would it be possible to change this? E.g. by making each project live
>>> on it's own branch. That would make the :ignored-files rules below a
>>> lot simpler.
>>
>> We could also make the rules simpler by adding support for the inverse
>> of :ignored-packages.
>
> Multi-package repositories are fundamentally incompatible with
> `package-vc` (they kind of work, but with various caveats).
They will have the same issues as elpa-admin has, right? In that case,
the issue will be if someone just wants to install prescient, they will
have all the other dependencies unconditionally "installed" along with
the rest. At the same time, if someone installs one of the more
specialised packages, which adds the same repository as a dependency,
you'll have the same package checked out twice, and I would have to
guess which takes priority in `load-path'...
> So I think we definitely don't want to support them better, but instead
> we should discourage them. If we want to invest efforts in that
> direction it should be efforts to make it easier to "re-merge" packages
> so as to move away from the problem.
Agreed.
next prev parent reply other threads:[~2022-11-20 15:41 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 [this message]
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
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=87wn7pljl3.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=okamsn@protonmail.com \
--cc=stefankangas@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/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).