search

wbond / package_control

The Sublime Text package manager
https://packagecontrol.io
4.8k stars 814 forks source link

The new package control version is ignoring all packages which I override some files #1155

Closed evandrocoan closed 10 months ago

evandrocoan commented 8 years ago

The new package control version is ignoring all packages which I override some files at the User Package folder

I override some default plugin files as these: image

With the older package control, prior to today update (19/09/2016), everything was working fine. Now those packages as the above Google Spell Checker are not being installed on a clean fresh install I use from here: https://github.com/evandrocoan/SublimeTextStudio#installation

If you follow those instructions, and let the Package Control install, it will miss several packages as the above. All the affected packages are marked as installed by this new Package Manger.

I have to uninstall them one by one, which will delete my configuration files as the ones above for the Google Spell Checker, and install them again, and restore my just deleted user settings at the Package folder. For now I will update those installation steps to go over this problem, only adding the user files after the Package Manger finishes installing everything.

How to revert to the older version?

If you are running into a bug, please read https://packagecontrol.io/docs/troubleshooting before submitting an issue here. Bug reports must include a debug log. The Troubleshooting page explains how to capture one.

wbond commented 8 years ago

If Package Control finds packages installed already, it won't try to overwrite them. What you should do is install the base packages first, then install your overrides.

The old version of Package Control functioned the same way. Most likely you just didn't notice because you added the overrides after installing the packages.

evandrocoan commented 8 years ago

Maybe I did not noticed, however this is one of the awesome Sublime's feature, I may override anything I want to from de default packages, or from the package manager packages at the Installed Package's folder. So, there is reason to why do not download the .sublime-package to the Installed Package's folder just because there is some files at the Use Package's folder. I am just saying to put the .sublime-packages at the Installed Package's folder, and let me naturaly override what I want to on the User Package's folder.

On Tue, Sep 20, 2016, 00:53 Will Bond notifications@github.com wrote:

If Package Control finds packages installed already, it won't try to overwrite them. What you should do is install the base packages first, then install your overrides.

The old version of Package Control functioned the same way. Most likely you just didn't notice because you added the overrides after installing the packages.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/wbond/package_control/issues/1155#issuecomment-248194630, or mute the thread https://github.com/notifications/unsubscribe-auth/AFFcvqoKR4-ycrfcWybypEKoHhf6mv8Pks5qr1iWgaJpZM4KBLr9 .

Att, Evandro Coan

wbond commented 8 years ago

The reason is that we cant assume a folder existing means it is an override. It could be a custom package with the same name. Overrides also don't exist in ST2.

There would need to be functionality added to detect something such as a file named .sublime-package-override, and if that exists, allow installing a package "underneath" the existing folder.

evandrocoan commented 8 years ago

I added two new code lines, and now it is working as I want to.

deathaxe commented 11 months ago

Fixed by Package Control 4