From: Georgios P. <pe...@ii...> - 2001-07-19 08:43:50
|
Hi all, In general I agree with the proposal of breaking things into small packages (and perhaps sub-packages) like the installerutils and the GUI related stuff. My only problem is what the interaction will be with TEA extensions. Usually, all my extensions are based on TEA, so at least under unix, I use configure/makefile. Shouldn't we have a way to extract useful information from the makefile at least i.e. regarding files that have to be installed etc. If we have to also specify things in a configuration file for the installer, perhaps will lead to (small) problems. Perhaps a script to automatically create the configuration script from TEA makefiles? I have tried to develop a cross-platform installer for one of my applications that followed the following procedure: It presented a GUI where the user could select things like the Installation dirs, etc. Then under unix, the installer was just a front-end to gunzip/tar/configure/make to do the job. Under windows, again it used gunzip/tar/make to simply install precompiled binaries. The needed executables came along with the installer. But I had plans to parse the makefile and extract from it the files that had to be copied. Also, I created shortcuts from plain tcl... Anyway, this introduction was simply because I have attached the code of this installer. Consider it under tcl licence:-) We can extract and use whatever parts of it we may find useful:-) If you think that anything from there should be turned into a package, I am willing to extract it... Regards, George |