I would rather have the installer create a install package with a unique name reflecting the GTK version but the executable to retain the name Ethereal.exe in each package. Many of my users already have shotcuts on their desktop that will be broken if the name of the executable actually changes. Either that or I have to make changes to the installer and manually rename the executable before packaging.
Since you can install Ethereal into a directory other then the default then having the same executable name should not cause a conflict for those who want to run both packages.
Hi List!
As there is a new Ethereal release proposed for the next week, I want to get some pending NSIS installer things done.
As Lars Roland stated, recent versions (from 2.0rc3 ?) of the NSIS installer has a *much* better compression algorithm included, called lzma. This reduces the size from the released 0.10.0 setup (about 13MB) to current CVS setup (about 9MB)!
I would like to switch to the NSIS's modern user interface, as it looks a lot better than the old one, and doesn't have any disadvantages I can see (beside the fact, that you will need a recent NSIS version to generate the installer itself).
For both reasons I would like to see the current NSIS 2.0 as "required", not "optional" as today, and put some information about that to the README.win32 file.
Ethereal GTK1 <-> GTK2
As the GTK2 version of Ethereal is quite stable now, we could think of releasing it in some "standard" way to the users.
I see two possible ways:
a) build two seperate installers for GTK1 and GTK2 versions (as in current CVS today)
b) build only one installer with both GTK versions in it
To b) using the lzma compression desribed above, this increases the installer size only in a moderate manner (with my current CVS files: GTK1: 9,1MB, GTK2: 9,7MB, both in one installer: 10,2MB).
It seems that both GTK version can be installed in one directory, there are no DLL naming conflicts or such, so there is no principle problem with this.
This will raise some more questions how the installer should handle some things,
but I would like to get some responses if b) is a good idea or not, before doing any further
investigation.
Do we want to add some default configuration files (cfilters, colorfilters, dfilters, preferences)?
I would tend to say yes. But as this topic isn't win32 specific, we should do this
for all platforms, not only win32. Even if other platforms are not able to install these files (just don't know if this is possible), there should be a basic set of configuration files at least available somewhere in CVS.
My personal believe to the whole thing, when reflecting some mailings in the past days is:
- require to use a current NSIS installer version (e.g.: 2.0 RC 3)
- use the modern NSIS user interface (MODERN_UI)
- using the lzma compression algorithm to reduce installer size dramatically
- put both Ethereal GTK versions 1 and 2 (together with the DLL's and such) into one installer
- put some example config files in CVS and install them with the installer
Comments on this?
Regards, ULFL
______________________________________________________________________________
Nachrichten, Musik und Spiele schnell und einfach per Quickstart im
WEB.DE Screensaver - Gratis downloaden:
http://screensaver.web.de/?mc=021110_______________________________________________
Ethereal-dev mailing list
Ethereal-dev@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-dev
