ActiveState Community
Navigation
RSS Feeds
Komodo upgrade reluctance
I noticed during the 4.3 installation that the install directory had changed from \Program Files\ActiveState Komodo Edit 4.x to \Program Files\ActiveState Komodo Edit 4. I'm hoping that this is a precursor to making future updates as patches instead of side-by-side installs? (I know this is possible with .MSI files under Windows, but I don't know how feasible it is under other operating systems.)
I say this because I'm reluctant to move to a new minor release because I have a whole Komodo ecosystem set up. :) When I install a new version, I have to reinstall extensions, move .pth files that are used by macros, and copy over color schemes. This is painful to start setting things up all over again. Even when Komodo has new, compelling features, I've been fairly slow to make the transition with the last few point upgrades.
So, are patch updates feasible for minor releases? Was this something you had planned already?
- Login to post comments
Now that we have moved to that install directly, updating form 4.3.1 to 4.3.2 should present no inconvenience. Do you mean instead going from 4.3 to 4.4? That is the idea, but you brought up a few edge cases that might make that difficult:
- extensions, not sure how this works
- .pth files, probably not covered
- color schemes and keybinding schemes - should be converted automatically?
We will still be using versioned preferences and allowing users to do side-by-side installs.
--
JeffG
Yes, I was meaning 4.3 to 4.4.
If (most) everything was converted during an upgrade, then it would certainly make things smoother. Any way that extensions could be detected in a previous version and offered to be brought over (provided the install.rdf allowed for it)?
I don't remember my color schemes converting over from 4.2 to 4.3, though that would be cool.
.pth files being moved over is probably unreasonable, true. :)