Armin Darvish

> Or perhaps make a preview key for every source (ripgrep-all is fast enough for 'any, but google is too slow, so C-o is ok). This is already possible with...

@bard Yes, the `:vc` install does not work, becuase of how the vc install tries to make the `.pkg` file. There is a quick fix for it you can do....

> 1. The files in `sources` with `Package-Requires` aren't parsed by any of the packaging systems, package-vc, melpa, straight, elpaca. Which is fine if that's how you like to maintain...

So one solution might be to move `consult-omni-embark.el` into a sub-directory. I am not willing to commit to supporting vc-install, yet, because it is new and there is likely going...

Yeah, I am not sure how much the package-vc would get worked on either, but I think if people start using it with all sorts of packages, then the issues...

@justinbarclay I tried my other package [consult-gh](https://github.com/armindarvish/consult-gh) with the vc install and it runs just fine even though I do have other files with `Package-Requires` declaration in the rool folder....

@bard The `:load-path` approach is not very convenient because updating and rebuilding, etc. has to be manual. `package-vc` has solved that but is still not as good as straight.el/elpaca and...

@justinbarclay Actually never mind, I figured out why `consult-gh` works. It reads the dependency on `consult-gh "2.2"` and installs that from MELPA instance!