CoolPackager is a program for developers which will allow users of your software to easily install your program. A CoolPackage is a self-extracting, and self-installing shell script. Creating a CoolPackage with CoolPackager only requires a .tar.gz and a simple installation script.
Why not use X10?
From what I understand, you would need place all your appliances close to your computer or have lots of wires around your house. But why not use X10 or and a program like heyu? Plus, lights are a lot funner to dim than to switch on and off.
Re: See also makeself
CoolPackager is basicly a project to teach me about C.
CoolPackager 0.4.1 understands --help, --info, and --extract to a limit. Help obviously displays a short summary on how to use the package. --info displays information about CoolPackager, but this is changing as I am writing 1.0. --extract puts the archive into package.tar.gz if users don't want to use the install script. In these packages I am also trying to make it very easy package (for example) for people to right click a package in gmc and see infomation about it. Check out a package and see the "CoolTags". Version 1.0 will also let users send options to the install script.
I am also thinking about an idea which will store package datestamps in a file. A package updating agent could look at this file, check the internet, and if a new update is available, download it.
I'm not tring to reinvent the wheel, but if you like makeself, go ahead use it. Nobody's forcing you to use CoolPackager. I can understand where you are coming from. CoolPackager 0.4.1 is okay compared to makeself, but by version 1.0 I expect to have it better coded, and be very flexible and compatible.
> makeself (by Stephan Peter) does the
> same job and is IMHO more general :
> the generated self extracting script
> understands a number of options as
> -info, -list, -lsm, -help, ...
> checksums and optionnally md5 sums are
> checked automatically before
> Makeself is very simple and actively
> maintained (check out the CVS version)