On Fri, Jun 3, 2011 at 3:14 AM, Adam
<geekdundee@gmail.com> wrote:
On Fri, 03 Jun 2011 17:58:42 +1000, Ged Murphy <
gedmurphy@gmail.com> wrote:
When I say wix, I mean windows installer. The two have become synonymous for me now.
Much of what you say isn't true.
The only issue I've ever come across with msi's is that failed installs can lead to the database becoming corrupt.
However this is very rare and can be repaired in various ways.
I get the feeling people use NSIS because it's open source and that must mean it's better/cooler.
I prefer to look at the merits of both open and closed and choose the best.
In 99% of cases, closed source comes out on top.
I must admit I am not a big fan of their clumsy syntax myself. Inno Setup seems better to me. As for open sourcedness - IMO its only really useful if you have the tools to edit the source. Bottom line is that I agree with this.
-----Original Message-----
From: Adam [mailto:geekdundee@gmail.com]
Sent: 02 June 2011 22:55
To: ReactOS Development List; Ged Murphy
Subject: Re: [ros-dev] 1294 [dreimer] Fix clean for cmake trees. ...
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 <gedmurphy@gmail.com> 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 <geekdundee@gmail.com> 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 <colin@reactos.org>
wrote:
dreimer@svn.reactos.org 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
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
_______________________________________________
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev
_______________________________________________
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev
--
Using Opera's revolutionary email client:
http://www.opera.com/mail/
_______________________________________________
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev