Maybe I am not understanding your comments but I would be very unhappy
if I had to maintain both the GTK1 and GTK2 developer environment
because the build did both. Is this what you meant by parallel? What are
you calling the installer? Are you talking the actual NSIS install
package? If so then why not let the developer build what version he
wants and then he can deliver it to his end user. I don't really
understand why the changes were made. Under the old make files, I could
build either GTK1 or GTK2 depending on the settings in the config.nmake.
Now it seems like this process has become way more complex then
necessary. I realize you are trying to make this easier and to work all
the bugs out but building in different directories isn't something that
I would want.
The simple thing here is to be able to specify in the config.nmake if
you want GTK1 or GTK2, The Ethereal_win32_libs will point to the
standard directory for the GTK modules necessary for that version. The
build would include the appropriate modules and the nsis packager would
do the same. Am I missing something here? Before the latest
modifications I did have to go to the packaging/nsis directory to make
the install package but that was a little step.
I don't mean to sound like such a critique but it seems like it is
becoming even more complicated then it already was. I look forward to
your new changes. Please don't take any of my comments personal.
Greg
>>> ulf.lamping@xxxxxx 1/30/2004 6:17:23 PM >>>
Hi List!
As previously announced and becoming a topic more and more at least
for
the win32 port.
With the installation process for the installer I've currently
changed,
you will have the opportunity to use the GTK1 or GTK2 version, but not
both.
The reason for this is e.g. that the name "ethereal.exe" is used for
both GTK versions 1 and 2, but there are other topics as well.
When installing to the same dir, I'm not sure if we will have DLL
conflicts. Currently this seems no problem, but this might be a
problem
in the future?
We have some options for a GTK2 installer:
1) put both GTK versions of Ethereal into the installer and simply
install them in parallel
2) build completely different GTK1 and 2 installer versions and
install
them in different dirs
to 1) questions:
a) the installler will be much bigger, is this ok? It has to include
both exe's and all different DLL's in parallel,
already about 13-14MB this will increase it by 4-5MB as an approx.
b) as all files in same dir, might getting problems in future versions
with DLLs with same names but different versions
c) how should the links / icons should be for both versions?
to 2) questions:
a) how to name the different versions? Has this to be reflected in the
Ethereal main version? E.g. Ethereal2.exe or Ethereal_gtk2.exe?
b) Same applies to the dir name to install into /registry keys and
such.
We could improve problem in 1)a) by seperating dissection and GUI
things. This would also reduce the size of the current installer also a
lot.
Currently the Ethereal and Tethereal exe's are statically linked,
although the dissection code is the same.
This will also apply on all other platforms as well?
I would tend to option 2), as this would make a clear distinguish
between the two versions. But this should be reflected in the main
Ethereal version too IMHO.
Any comments?
Regards, ULFL
_______________________________________________
Ethereal-dev mailing list
Ethereal-dev@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-dev
