ASPN ActiveState Programmer Network
ActiveState
/ Home / Perl / PHP / Python / Tcl / XSLT /
/ Safari / My ASPN /
Cookbooks | Documentation | Mailing Lists | Modules | News Feeds | Products | User Groups


Recent Messages
List Archives
About the List
List Leaders
Subscription Options

View Subscriptions
Help

View by Topic
ActiveState
.NET Framework
Open Source
Perl
PHP
Python
Tcl
Web Services
XML & XSLT

View by Category
Database
General
SOAP
System Administration
Tools
User Interfaces
Web Programming
XML Programming


MyASPN >> Mail Archive >> komodo-beta
komodo-beta
Re: [Komodo-beta] 4.4
by Trent Mick other posts by this author
May 14 2008 11:59AM messages near this date
view in the new Beta List Site
[Komodo-beta] 4.4 | Re: [Komodo-beta] 4.4
[Lindsay wrote]
>  I ran the installer (XP SP2) but I can't see that it has done anything :
>  when I run what ought to be the new komodo it appears to be 4.3!

[Michael wrote]
>  I had the same problem - tried to do an upgrade install of 4.4.0a1 but still
>  got 4.3. Uninstalling Komodo and reinstalling 4.4.0a1 fixed it here too.

[Conor wrote]
>  I had exactly the same problem. It could be that you didn't restart
>  the computer and the older libraries are in use?

[Ian wrote]
>  I got the same issue. Installing on windows on top of an existing 4.3 
>  installation. The install goes into the same directory as the old 4.3 
>  install and seems to overwrite some but not all of the files. Ie I see 
>  files with newer times but the about box still says 4.3 and the new 
>  features aren't available.

Is it possible that you had Komodo 4.3 *running* when you installed 
Komodo 4.4.0a1 into the same directory? I believe that would result in 
the behaviour you saw.

I haven't yet been able to reproduce this problem with Komodo 4.3 *not* 
running. I will try to repro by installing 4.4.0a1 when 4.3 is already 
running to test my theory.

In any case, my plan is to change the installer to require the target 
directory to be empty to do the install -- to ensure you don't install 
over an existing Komodo installation. This is for two reasons:
1. It might be surprise to some that they use the same install dir.
2. Installing two different MSIs (with different MSI ProductCode's) to 
the same directory can make the MSI system unhappy. Reference counting 
is done on files in the install area so uninstall gets complex and, in 
my experience, unreliable.

Unfortunately I won't (at least not easily) be able to get the install 
to detect another Komodo installation in the same dir and uninstall it 
properly before proceeding with the install.


Trent

-- 
Trent Mick
trentm at activestate.com
_______________________________________________
Komodo-beta mailing list
Komodo-beta@[...].com
http://listserv.ActiveState.com/mailman/listinfo/komodo-beta
Thread:
Lindsay Marshall
Trent Mick
Ian MacLean
Trent Mick
Lindsay Marshall
Conor Kerr
Michael Geary
Ian MacLean
Troy Topnik

Privacy Policy | Email Opt-out | Feedback | Syndication
© 2004 ActiveState, a division of Sophos All rights reserved