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

[Okamsn]

On 2022-12-05 15:21 UTC, Stefan Monnier wrote:
>> 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?
>
> `load-path` is a list of directories, so you can only control which
> files are included by controlling which directories are included.
>
> But I don't understand the question coming from you: as a developer of
> the package, how do *you* control that (since, presumably, you use that
> same file layout as used in the Git repository)?
>
>
>          Stefan
>

If you are asking whether I add the Git repository itself to the load
path for testing packages, I do not. Instead, I have been using
Straight.el (https://github.com/radian-software/straight.el) to install
development versions of packages, which can download the repository once
but only install the files and needed dependencies (according to a
specification) by linking/copying those compiled files to another
directory, which is then added to the load path.

For Prescient in particular, it makes sense to have the files in a
single repository, since a change in the main file can mean changes in
the extension files and vice versa (as a single conceptual step in
development). However, testing the development version of an extension
for one UI (such as for Vertico) doesn't necessarily mean wanting to use
the development version of another UI's extension (such as for Company)
or wanting to install another extension's dependee UI package (such as
Selectrum, which was soft-deprecated in favor of Vertico).

Is this what you are asking?

Really, I was wanting to ask whether package-vc installs all of the
ELisp files in a repository or whether it installs the files according
to the ELPA spec or a provided spec. I see that the user option
`package-vc-selected-packages` does not mention the `:ignored-files`
entry that the ELPA spec uses, so I was wondering.

The documentation string for `package-vc-checkout` mentions a
`package-vc-link-directory`, but I don't see that in the file. Did that
become `package-vc-install-from-checkout`?