From: Philip Kaludercic <philipk@posteo.net>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
Jonas Bernoulli <jonas@bernoul.li>,
emacs-devel@gnu.org
Subject: Re: [nongnu] main f4166f428a: * elpa-packages (emacsql): New package.
Date: Thu, 15 Dec 2022 21:05:59 +0000 [thread overview]
Message-ID: <87pmckgyx4.fsf@posteo.net> (raw)
In-Reply-To: <CADwFkmkuptC11w-tL46JKvwqdMq9g4et3uqjKE63VdMPKFAUpg@mail.gmail.com> (Stefan Kangas's message of "Thu, 15 Dec 2022 12:37:58 -0800")
Stefan Kangas <stefankangas@gmail.com> writes:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
>> But none of the packages in (Non)GNU ELPA depend on emacsql-<backend>,
>> so we don't really need to abide by the Melpa packaging.
>
> The main reason I've added emacsql to NonGNU ELPA is to be able to add
> packages that depend on it (such as org-roam). Those packages currently
> depend on emacsql-<backend> packages.
Do you think it is plausible to get org-roam to switch to emacsql
without any specific subpackage?
>>> If we want to add those packages as is, and have them installable,
>>> their dependencies must also be in NonGNU ELPA.
>>
>> I expect that can be changed when needed.
>
> Agreed. Let's see what Jonas thinks about the plan I proposed.
next prev parent reply other threads:[~2022-12-15 21:05 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
2022-12-15 16:10 ` Stefan Monnier
2022-12-15 20:37 ` Stefan Kangas
2022-12-15 21:05 ` Philip Kaludercic [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pmckgyx4.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=emacs-devel@gnu.org \
--cc=jonas@bernoul.li \
--cc=monnier@iro.umontreal.ca \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.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.