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

[Okamsn]

On 2022-11-20 17:42 UTC, Okamsn wrote:
>>
>>> 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.
>
> I wouldn't mind making new branches that hold the stable versions. Are
> you OK with the README and CHANGELOG still being duplicated in that case?
>
> ...

After communicating with the other maintainers, they are requesting that
I do not make this change (discussion here:
https://github.com/radian-software/prescient.el/issues/138).

You mentioned that there are caveats for package-vc. If a user wanted to
install a package using that feature (which I look forward to trying),
is it possible to tell it the files that should be added (or not be
added) to the load path?

>>> When I tried testing the installation of `prescient`, it installed
>>> an older version of the file `prescient.el` than what is current in the
>>> repository. This was the version that received an update to the version
>>> number, but how does the system decide which is the most recent stable
>>> version of a file? I might need to increase the number to make it
>>> install a newer version.
>>
>> Yes, ELPA finds the last commit that changed the version header and uses
>> that to prepare a release.
>
> OK. I will try updating the version number to make sure that was the
> problem.
>

This was the problem.  The installation works after changing the version
number. I have asked about the author's process for releasing a new
minor version.