auto-updater and .app filename
Hi,
Last week, I got offered an update to PHPStorm 2 (2.0.1). Where in the early access of PHPStorm, the IDE would auto-update itself, now I had to go to my browser, download the package, and install it. Quite a hassle if you ask me, while there is apparently some auto-updated logic available.
Additionally, the binaries that I then have to install have a different name (PhpStorm 2.0.1 instead PhpStorm 2.0), which is rather annoying because if this keeps working this way, my Applications folder will be littered with PhpStorm * binaries)...
Are there plans to fix this?
请先登录再写评论。
hm, a Jetbrains employee told me to post this question here, but I seem to get no response here. Any Jetbrains people here that can clear this up?
Well, we aware of current state of things consider this a (very) low priority task.
Is there a reason for giving this such a low priority, given the fact that it used to work in the early access releases?
It was made specifically for *weekly* EAP builds because they are published so often.A courtesy to our voluntary testers.
Also, the patch known to have problems with Windows 7 UAC and some OS X & Linux installations, thus we don't provide patch for release builds.
OK thank you, that at least clears part of it up. Then the last thing: Why not have the final executable keep the same name throughout releases (so just "PhpStorm2" instead of the current naming conventions of having a seperate name for each minor release, thereby cluttering the Applications folder)?
Well.. all builds are done completely automatically and this is the way we name our products now across all platforms. This may change in future. Low prio, however.
i delete the phpstorm folder in my program files before installing a new EAP.. then just install to /phpstorm/ without the number.. defs helps.. the settings are stored elsewhere so dont worry bout loosing any of those