Projects / CoolPackager

CoolPackager

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.

Tags
Licenses
Operating Systems
Implementation

Recent releases

  •  29 Jun 2001 05:22

    Release Notes: This release has more support in using CoolTags (my invention), and collects more information about your software, and if your package has interactivity, then it will display this information when you type packagenamehere --info. There is also a fix for a bug that made interactive packages not valid shell scripting, which would create errors in some cases.

    •  06 May 2001 06:21

      Release Notes: This release now includes the ability to make your packages somewhat interface, with --help and --extract options.

      •  04 May 2001 04:56

        Release Notes: This program now makes a shell script instead of self compiling C programs. The user no longer requires gcc to install a CoolPackage.

        •  22 Apr 2001 01:01

          Release Notes: Names of output files don't have to end in .c, and the name of an output file can be changed after it's written.

          •  14 Apr 2001 02:57

            Release Notes: Ability to make Web scripts (what makes the command http://www.ccil.org/~sharp/cpkg | sh work).

            Recent comments

            07 May 2001 16:53 csharph

            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
            > extraction
            > Makeself is very simple and actively
            > maintained (check out the CVS version)
            >


            07 May 2001 13:15 petitjean

            See also makeself
            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 extraction
            Makeself is very simple and actively maintained (check out the CVS version)

            Screenshot

            Project Spotlight

            OpenStack4j

            A Fluent OpenStack client API for Java.

            Screenshot

            Project Spotlight

            TurnKey TWiki Appliance

            A TWiki appliance that is easy to use and lightweight.