Update 4.0.1 to 4.0.2 as new installation - really?????

I think PHPStorm is the last application in the universe that hasn't an automatic update feature.
Though this may be OK when updates come every few months - when I have to go through the whole process (close phpstorm, download, install, rename links in the launcher, hope everything goes well....) for even a minor release (from .0.1 to .0.2 for gods sake) I am thoroughly hindered in my development.

Am I the only who thinks this is a major pain in the lower end of the back?

5 comments
Comment actions Permalink

Last time i updated it was v3 to v4 it was rather quick considering i just installed v2.5 not so long ago. Hope authors dont pick up tendency from firefox where they increase version every minor release to catch up with internet explorer v12

0
Comment actions Permalink

... when I have to go through the whole process (close phpstorm, download, install, rename links in the launcher, hope everything goes well....) ...



I development solely in linux and avoid the above nonsense by doing the following:
  • Untar the latest release into a standard place like /opt (I just use /opt/[whatever it untars to])
  • Create a symlink /opt/phpstorm that points to the new release


On upgrades I merely relink phpstorm to the new release directory.  I don't have to change my launchers or anything. It's pretty simple to upgrade then. Plus you can always downgrade to a previous version should something go awry. :)

0
Comment actions Permalink

You just missed one interim update.

We'll try to make the patch system more smart - to suggest user a sequential update in such case.

0
Comment actions Permalink

Thank you Alexey,

I really dont mind updateing "by hand" if necessary - but a 0.0.1 step shouldn't make me do that - it just drags the attention to a whole different process (updating) than I wanted to do.
So if its once in a while: no problem. If it starts to bugger me (i.e. when I start to ask myself if I should start phpstorm for this litttle change or just make it in np++): bad

So im looking forward to the simpler update process.

Greetings
Johannes

0
Comment actions Permalink

The same issue occured to me, I didn't install the previous minor patch because it had a strange version number (I think 4.0, while I had 4.0.1 installed)

The windows installer should also suggest to update the installed product rather than installing it as a new version.

I installed it over the previous installation path and I have both 4.0.1 & 4.0.2 in "add/remove programs", i'm sure that after uninstalling one of them it will break the other

0

Please sign in to leave a comment.