If the original author of Package Control is unable or unwilling to sign and upload a new version to packagecontrol.io
, then maybe SublimeHQ should step in to update their installer script in Default/install_package_control.py
and download the latest version directly from the GitHub releases instead. I wonder how much security is gained by using the signed, but old and non-operable version of Package Control, over just pointing the download link to the asset from https://github.com/wbond/package_control/releases/latest (or even to hardcode some working tagged release of Package Control 4.0).
I mean I’m not personally affected by this “bug”, but if I were a new user and the first thing after installing Sublime Text needs to be to research on GitHub issues or forum threads in to understand that I have to manually find and download a working Package Control version, then I would probably be already put off by that hassle…