Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Accidentally introduced runtime dependency on package.el #43

Closed
raxod502 opened this issue Jun 14, 2017 · 2 comments
Closed

Accidentally introduced runtime dependency on package.el #43

raxod502 opened this issue Jun 14, 2017 · 2 comments

Comments

@raxod502
Copy link
Member

We need package.el for package-built-in-p at runtime, so we know whether or not to signal an error due to a missing package. Unfortunately, this means we now have a runtime dependency on package.el. I think the most amusing way to solve this problem is to persistently cache the complete list of built-in packages, and update the cache whenever we detect that the output of M-x emacs-version has changed.

@raxod502 raxod502 added this to the 1.0 milestone Jun 14, 2017
@raxod502 raxod502 mentioned this issue Jun 14, 2017
56 tasks
@raxod502
Copy link
Member Author

This would also fix the issue of all recipe repositories being cloned looking for a recipe for emacs.

@raxod502
Copy link
Member Author

raxod502 commented Dec 9, 2017

Amusing as my original idea might have been, it makes way more sense to just use finder-inf, which (it turns out) has a nice alist of all the packages that are considered "built-in".

There's now no dependency on package.el at any point, runtime or compile time.

@raxod502 raxod502 closed this as completed Dec 9, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant