Re: [nongnu] main f4166f428a: * elpa-packages (emacsql): New package.

[Jonas Bernoulli]

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.
>
>>> 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.

I am super busy and would like to delay thinking about this and working
on it until next year.

I might actually come to the conclusion that not splitting up the
package is the right way to go in this case.  Or the backends that--to
the best of my knowledge--nobody uses (all the non-sqlite backends),
could be moved to separate repositories.  Eventually -sqlite-builtin
will be the default backend, but we still need -sqlite-module, for older
Emacs releases.  I intend to deprecate the original -sqlite backend
(which uses a custom executable) in a few months, and I intend to then
remove it from the repository (to get rid of the tracked sqlite.c), but
keep it alive in a separate repository for a while.