Re: Adding the `prescient` packages to NonGNU ELPA?

[Philip Kaludercic]

Okamsn <okamsn@protonmail.com> writes:

> On 2022-12-17 16:24 UTC, Philip Kaludercic wrote:
>> Philip Kaludercic <philipk@posteo.net> writes:
>>
>>> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>>
>>>>> The only issue I can think about is if later on someone else wants to
>>>>> add a package that depends on a specific "sub-package", and they find
>>>>> themselves in a conflict specifying their dependency list, in case this
>>>>> hypothetical package is to be distributed both via ELPA and MELPA.
>>>>
>>>> Not our problem?
>>>
>>> So let it be written, so let it be done.
>>>
>>> I will prepare the package with everything bundled into a single
>>> package, and see if that works out.
>>
>> As I had suspected, the main issue is that byte-compilation fails:
>> ...
>> But I guess this can be resolved upstream, if there is an interest.
>
> The extension packages each require the version of the UI that they work
> with. I think it is reasonable to do that, and I don't foresee the other
> maintainers wanting to change that.
>
> Is there a way to fix this while still declaring the extension packages'
> requirements?

In practice, will this be a problem?  As you can see in the -pkg.el
file, so the other packages won't be added to the list by defaut:

--8<---------------cut here---------------start------------->8---
;; Generated package description from prescient.el  -*- no-byte-compile: t -*-
(define-package "prescient" "6.1.0" "Better sorting and filtering" '((emacs 
"25.1")) :commit nil :authors '(("Radian LLC" . 
"contact+prescient@radian.codes")) :maintainer '("Radian LLC" . 
"contact+prescient@radian.codes") :keywords '("extensions") :url 
"https://github.com/raxod502/prescient.el";)
--8<---------------cut here---------------end--------------->8---

If loaded, an error will be raised.