From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Andreas Pflug" <pgadmin(at)pse-consulting(dot)de> |
Cc: | <jm(dot)poure(at)freesurf(dot)fr>, <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: pga3 website |
Date: | 2003-08-05 20:27:55 |
Message-ID: | 03AF4E498C591348A42FC93DEA9661B83AF1B9@mail.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
> -----Original Message-----
> From: Andreas Pflug [mailto:pgadmin(at)pse-consulting(dot)de]
> Sent: 05 August 2003 21:10
> To: Dave Page
> Cc: jm(dot)poure(at)freesurf(dot)fr; pgadmin-hackers(at)postgresql(dot)org
> Subject: Re: [pgadmin-hackers] pga3 website
>
> >
> Most of this stuff is necessary for this VB s**t, but not for
> pgAdmin3.
> We don't have referenced files,
No? Have you looked at the .exe using dependency walker? There are quite
a few dependencies, though thankfully we don't need to distribute them
at the moment *unless* we release a debug build. If we ever move to a
less static build the we may have things like libpq.dll and wx.dll.
There was also talk at one point of using the Microsoft CHM viewer under
Windows.
> cleanup is simply delete, repair is
> install new, there are no conflicting files, ...
Yes, at the moment.
>
> But if you can suggest an open-source installation tool, this is
> certainly more "state of the art".
I'm not after state of the art for the sake of it. The major reasons I
use MSI are:
a) Easily scriptable for any msi file for automated installation
b) Allows use/creation of merge modules for easy bundling of software -
something Jean-Michel is extremely keen on.
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Pflug | 2003-08-05 21:09:23 | Re: pga3 website |
Previous Message | Andreas Pflug | 2003-08-05 20:10:00 | Re: pga3 website |