Michael Van Canneyt <mich...@freepascal.org> wrote: > > > On Wed, 20 Jan 2010, Graeme Geldenhuys wrote: > > > Vladimir Zhirov wrote: > >> > > The clients we are targeting are all newcomers to Linux. They are > > used to Windows with simply double clicking a setup.exe file. This > > is our goal for Linux to - no opening of command prompts and typing > > (unless you are an expert or are doing a remote install via SSH). > > > > > >> InnoSetup has the advantage of PascalScript, that makes it easier > > > > I have heard of PascalScript, but have no idea what it really is or > > how it works. Does FPC support it? I'll have to investigate this > > further, as it might be a nice cross-platform single source script > > solution. > > > > > >> * Familiar syntax of configuration files/scripts. > > > > Please explain?
Michael Van Canneyt wrote: > If you want to script your install in InnoSetup, you use pascal. > A definite advantage for all Delphi/FPC people. This is the first part of explanation. And the second part is the suggestion to take as much as possible from configuration and script file syntax of some existing open source installation system. This way users would not have to learn new system from the scratch and could reuse their knowledge. There is no need to maintain full compartibility, just to take most important ideas. The good example of this approach is fpGUI itself - it is not compatible with LCL/VCL but it is easy for LCL users to understand the meaning of fields and methods because they have familiar naming. I would like it very much if migration between InnoSetup and new installation system were as easy as migration between LCL and fpGUI. And PascalScript could help to make it so. -- Best regards, Vladimir Zhirov -- _______________________________________________ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
