From: Stefan Kangas <stefankangas@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Jonas Bernoulli <jonas@bernoul.li>, emacs-devel@gnu.org
Subject: Re: [nongnu] main f4166f428a: * elpa-packages (emacsql): New package.
Date: Tue, 13 Dec 2022 10:52:38 -0800 [thread overview]
Message-ID: <CADwFkmmoho-5Z7KyEG9tk1Wa-=BFrDrhkB8dtttd+OuZFRCTPg@mail.gmail.com> (raw)
In-Reply-To: <jwvfsdjcqff.fsf-monnier+emacs@gnu.org>
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> To me this looks completely ridiculous: why split this into N packages,
> when each one is tiny anyway.
The reason I did it like that is only that it was the path of least
resistance: it replicates what is currently there on MELPA. This
matters because other packages depend on the existence of e.g. the
`emacsql-sqlite' package.[1] If we want to add those packages as is, and
have them installable, their dependencies must also be in NonGNU ELPA.
> Let's stop the madness and make it a single package.
> Nobody (neither we, nor the users) benefits from having such tiny packages.
I see three options here:
1. We could make transitional packages on NonGNU ELPA that just depend
on `emacsql'.
2. We can change the packages to be transitional on MELPA, too.
3. We can make _only_ the existing packages on MELPA transitional.
With option 2 or 3, I think we could convince maintainers to simply
depend on `emacsql' instead. This should be done before adding the
packages to NonGNU ELPA (so we don't need any transitional packages
there).
Footnotes:
[1] https://melpa.org/#/emacsql-sqlite
next prev parent reply other threads:[~2022-12-13 18:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <167091741978.18640.16217484079810212983@vcs2.savannah.gnu.org>
[not found] ` <20221213074340.1C45BC000CE@vcs2.savannah.gnu.org>
2022-12-13 14:50 ` [nongnu] main f4166f428a: * elpa-packages (emacsql): New package Stefan Monnier
2022-12-13 18:52 ` Stefan Kangas [this message]
2022-12-15 16:10 ` Stefan Monnier
2022-12-15 20:37 ` Stefan Kangas
2022-12-15 21:05 ` Philip Kaludercic
2022-12-16 0:19 ` Stefan Kangas
2022-12-17 1:31 ` Jonas Bernoulli
2022-12-17 2:01 ` Jonas Bernoulli
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='CADwFkmmoho-5Z7KyEG9tk1Wa-=BFrDrhkB8dtttd+OuZFRCTPg@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jonas@bernoul.li \
--cc=monnier@iro.umontreal.ca \
/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).