"As far as I'm aware that is a start-on-demand service which only starts up
if you run a MSI installer"

i confirm this

On Fri, Jun 3, 2011 at 2:24 AM, Zachary Gorden <[email protected]>wrote:

> I intend to package the BE so that you have one installer for the various
> platform targets instead of the current three installers we have right now.
> I am not familiar enough with NSIS to know why Daniel did not do this,
> though from his complaining I got the impression he didn't try to get any
> fancier with the NSIS installer because he didn't want to go through the
> trouble of futzing with it.  One could argue that since we need little
> beyond installing files and making sure that an uninstallation actually
> cleans up the files and shortcuts, the best option is MSI since an MSI
> installer actually registers with the OS the things that need to be cleaned
> up when an application is to be uninstalled.
>
> Also a correction to your comment about the MSI service.  As far as I'm
> aware that is a start-on-demand service which only starts up if you run a
> MSI installer.  It'll hang around for a bit afterward, but then turns itself
> off if you don't run another installer for a while.
>
>
> On Thu, Jun 2, 2011 at 5:11 PM, Adam <[email protected]> wrote:
>
>> Fair enough, but does RosBE actually do anything (installer-wise) other
>> than install its files in a directory and set the occasional environment
>> variable (PATH) - if this is the case, surely any installer (be it NSIS,
>> Inno Setup, MSI, etc) can do this.
>>
>>
>> On Fri, 03 Jun 2011 08:03:07 +1000, Zachary Gorden <
>> [email protected]> wrote:
>>
>>  The amount of functionality that MSIs offer comes with a price.  Some of
>>> us
>>> believe it is worth it.  Some don't.  We, meaning Daniel and myself, want
>>> a
>>> MSI installer.  If someone else wants to maintain the NSIS installer, we
>>> will not stop them.  We just won't offer any help doing so since we
>>> (Daneil
>>> and myself) want a MSI installer.
>>>
>>> On Thu, Jun 2, 2011 at 4:55 PM, Adam <[email protected]> wrote:
>>>
>>>  So having a service running all the time just to install programs, and
>>>> having to not be able to uninstall a program cleanly if the MSI file has
>>>> been moved/deleted (or if the MSI file that was copied into some obscure
>>>> place in the %SYSTEMROOT% path) or due to some other sort of failure,
>>>> provides an error, is clean is it? Not to mention it will be impossible
>>>> to
>>>> uninstall in Safe Mode (should it be necessary) since MSIEXEC refuses to
>>>> run
>>>> under Safe Mode these days.
>>>>
>>>> Never tried WiX before, but the problem wouldn't be WiX - it would be
>>>> MSIEXEC and the way it works.
>>>>
>>>>
>>>> On Fri, 03 Jun 2011 07:35:56 +1000, Ged Murphy <[email protected]>
>>>> wrote:
>>>>
>>>>  Are you serious? Have you ever used WiX in a serious capacity?
>>>>
>>>>> It's far superior to NSIS in pretty much every way.
>>>>>
>>>>>
>>>>> On 2 June 2011 22:18, Adam <[email protected]> wrote:
>>>>>
>>>>>  I do not like the idea of moving to Windows Installer for RosBE 2.0 -
>>>>>> it
>>>>>> can
>>>>>> be quite tedious to clean up if the install is half done. IMO the
>>>>>> original
>>>>>> installer (NSIS) is much more cleaner than Windows Installer too.
>>>>>>
>>>>>> If it ain't broke don't fix it I say.
>>>>>>
>>>>>> On Fri, 03 Jun 2011 06:52:17 +1000, Colin Finck <[email protected]>
>>>>>> wrote:
>>>>>>
>>>>>>  [email protected] wrote:
>>>>>>
>>>>>>>  > if not exist "CMakeLists.txt" (
>>>>>>>
>>>>>>> Can we decide on dropping support for rbuild stuff in RosBE 2.0?
>>>>>>> Reasons:
>>>>>>>
>>>>>>> - RosBE 2.0 will certainly come with an updated set of build tools.
>>>>>>>  (GCC 4.6 with mingw-w64 target is planned, maybe even a multilib
>>>>>>>  version)
>>>>>>>  The target change already makes older builds uncompilable with RosBE
>>>>>>>  2.0. Even if this would be fixed, nobody would guarantee you that a
>>>>>>>  revision built with RosBE 2.0 behaves the same as one compiled with
>>>>>>>  1.5.x.
>>>>>>> - Several versions of RosBE can be installed parallely, especially if
>>>>>>>  you're also moving to a Windows Installer for RosBE 2.0, which
>>>>>>> doesn't
>>>>>>>  care about Uninstall entries of NSIS. So everybody has the option
>>>>>>>  to build older rbuild-powered revisions at any time.
>>>>>>> - It could make all scripts cleaner again :-)
>>>>>>>
>>>>>>> Regards,
>>>>>>>
>>>>>>> Colin
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Ros-dev mailing list
>>>>>>> [email protected]
>>>>>>> http://www.reactos.org/mailman/listinfo/ros-dev
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> --
>>>>>> Using Opera's revolutionary email client: http://www.opera.com/mail/
>>>>>>
>>>>>> _______________________________________________
>>>>>> Ros-dev mailing list
>>>>>> [email protected]
>>>>>> http://www.reactos.org/mailman/listinfo/ros-dev
>>>>>>
>>>>>>
>>>>>>  _______________________________________________
>>>>> Ros-dev mailing list
>>>>> [email protected]
>>>>> http://www.reactos.org/mailman/listinfo/ros-dev
>>>>>
>>>>>
>>>>
>>>> --
>>>> Using Opera's revolutionary email client: http://www.opera.com/mail/
>>>>
>>>> _______________________________________________
>>>> Ros-dev mailing list
>>>> [email protected]
>>>> http://www.reactos.org/mailman/listinfo/ros-dev
>>>>
>>>>
>>
>> --
>> Using Opera's revolutionary email client: http://www.opera.com/mail/
>>
>
>
> _______________________________________________
> Ros-dev mailing list
> [email protected]
> http://www.reactos.org/mailman/listinfo/ros-dev
>
_______________________________________________
Ros-dev mailing list
[email protected]
http://www.reactos.org/mailman/listinfo/ros-dev

Reply via email to