-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
The :depends keyword does not take package ownership into account #9134
Comments
But in this case the |
Just realized that it needs to do that, too. |
@Stebalien @skebanga Can you try #9136 |
First time I've done this, so not sure if it's correct, although I believe it is (followed instructions here)
Restarted spacemacs and the warnings went away Reverted to develop
Restarted spacemacs and the warnings were back. So for me, looks like it's workin! Thanks @TheBB |
Hm. Maybe I'm experiencing a different issue? My problem is that helm is getting installed because:
|
I'll solve this but it may be a few days. |
I have updated the PR. @Stebalien I think it should fix your problem. Please let me know. |
With the latest changes I am able to re-enable ivy (disabling helm) and cleanly launch rather than failing in eieio... |
I also tested on |
Still broken for me. Describe package gives:
|
I've tried removing the So, maybe this doesn't have anything to do with "unowned" packages? The one thing that fixes this for me to change the shell layer's helm dependency to: (helm :toggle (configuration-layer/layer-usedp 'helm)) That results in a warning about the shell layer not owning the helm package but also prevents the helm package from getting installed. However, it appears that simply removing the helm dependency from that package doesn't prevent it from being installed. |
Is the problem that the helm package is being downloaded or that it's being configured and enabled? |
Helm is only being downloaded, not configured (although it still shouldn't be downloaded in this case). However, the other packages (the ones that declare |
With the latest version of my PR I can't verify the latter problem you have. I get
|
Sorry, I accidentally posted too soon. Here's the real comment. @Stebalien I have updated the PR again. Please have a look. Depending on your exact config, you will probably find that the helm package is still being installed, because the following packages (at least, there may be more) depend on it (not in the Spacemacs
If you found that the helm package was not installed previously and that any of these four packages (or some I have not discovered) were used in your config, I can only assume that was a bug that has been fixed, because we cannot in good conscience override the dependencies that package authors have decided to use. Now, whether any of these packages need to be declared with |
I'll rename |
Should be fixed in develop. |
@TheBB The latest version (the one merged into develop) works. Thanks! (FYI, I had already already excluded those packages for precisely this reason.) |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please let us know if this issue is still valid! |
Description
The layer packages
:depends
keyword does not take package ownership intoaccount. That is, if a layer declares a package in
<layer>-packages
butdoesn't initialize it (doesn't own it), the
:depends
keyword will still treatthe package as if it were available.
For example, given:
layers/foo/packages.el
:layers/bar/packages.el
:bar
will be installed (andfoo
along with it if thebar
package actuallydepends on
foo
).System Info 💻
The text was updated successfully, but these errors were encountered: