Don't always kill litestep.exe at the beginning of the installation
Reported by Tobbe Lundberg | January 15th, 2009 @ 01:12 PM | in LOSI 0.4
Currently if a litestep.exe process is detected during the install this process is killed. This is done to make it possible to upgrade the LiteStep you are currently using. However, if no litestep.exe is found in the directory the user is installing to, it isn't needed to kill litestep.exe.
Of course it needs to be killed at the end of the installation when we're about to launch the new LiteStep.
Comments and changes to this ticket
-
Tobbe Lundberg January 15th, 2009 @ 02:26 PM
- State changed from “new” to “maybe”
-
Tobbe Lundberg January 15th, 2009 @ 02:36 PM
- Milestone set to “LOSI 0.4”
-
Tobbe Lundberg January 16th, 2009 @ 11:08 PM
- State changed from “maybe” to “resolved”
(from [366b9944381fa61ea51fd7b5d72ddc0474f953f6]) Added a check to make it less likely we kill litestep.exe if we don't have to when extracting files. [#3 state:resolved] http://github.com/Tobbe/losi/com...
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
LiteStep OpenSource Installer
People watching this ticket
Tobbe Lundberg
Referenced by
-
7
Confusing output when extracting files
Best option would be to solve issue #3 removing the
need ...
-
3
Don't always kill litestep.exe at the beginning of the installation
(from [366b9944381fa61ea51fd7b5d72ddc0474f953f6]) Added a...
-
9
Evar settings doesn't take affect during install
Now, after solving issue #3 this only happens when instal...
-
7
Confusing output when extracting files
Since issue #3 is resolved, this issue is no longer valid.