User talk:Red Wine: Difference between revisions

From NSIS Wiki
Jump to navigationJump to search
(NSIS SFX Package Builder)
(→‎NSIS Quick Setup Script Generator issue: -- seems to be fruitless to have this here. :()
 
(4 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== NSIS SFX Package Builder ==


== NSIS SFX Package Builder ==
Just another sfx package creator written in whole using NSIS scripting lang. Possible benefit from its use is the small size of the sfx container because of its lzma compression and the small NSIS header. Another benefit, hopefully, is its easy of use. Requires an active NSIS installation on the system where compiling the container.


== NSIS SFX Package Builder ==
== Installer for Successional Installations ==


Just another sfx package creator written in whole using NSIS scripting lang. Possible benefit from its use is the small size of the sfx container because of its lzma compression and the small NSIS header. Another benefit, hopefully, is its easy of use. Requires an active NSIS installation on the system where compiling the container.
I like your example script [[Installer for Successional Installations]]. I've made a page on [[Embedding other installers]] describing how to install other installers. I am considering updating it to use your technique for successional installs.
 
I might make the second example script part of a sourceforge project. Perhaps a NSI that will download all the requested installers, generate a NSI that auctually installs them compile the NSI. I would not want to redistribute all the installer files, nor could I, and I don't think a mega installer that installs every app imaginable would be the best of ideas either.

Latest revision as of 08:12, 13 September 2013


Installer for Successional Installations

I like your example script Installer for Successional Installations. I've made a page on Embedding other installers describing how to install other installers. I am considering updating it to use your technique for successional installs.

I might make the second example script part of a sourceforge project. Perhaps a NSI that will download all the requested installers, generate a NSI that auctually installs them compile the NSI. I would not want to redistribute all the installer files, nor could I, and I don't think a mega installer that installs every app imaginable would be the best of ideas either.