Language Selection

English French German Italian Portuguese Spanish

InstallJammer, a self-executing installer for Linux

Filed under
Software

In the crowded Linux packaging landscape, it would be easy to overlook Damon Courtney's InstallJammer. However, InstallJammer, which provides self-executing installers for Linux and other operating systems is well worth a look. Version 1.1 was released recently with a number of new features, including support for RPM and Debian package databases, console-based installs, new platforms, and much more.

Program features

After starting InstallJammer the first time, an empty project manager will appear and a wizard will guide you through the setup of your first project. It asks for your company name, version information, and asks for the main directory, where all the program files are located. So it's a good idea to use ./configure --prefix=/home/user/programdir to compile the sources, so that all the files are in one spot.

The install builder itself sports a common tree structure on the left of the project manager wizard with all the steps you'll use to build a perfect installer. Go through the steps from top to bottom and you'll have your installer.

On the right side of the wizard, you can change the settings.

Full Story.

More in Tux Machines

Android Leftovers

Leftovers: OSS

Ubuntu 16.04 Review: What’s New for Desktop Users

Ubuntu is a tricky distribution. As much as I love it on my home server, my desktop is a different ballgame. In my experience, releases between LTS versions have many new technologies that may or may not survive in the next LTS. There were many technologies or features that Canonical thought were ambitious -- HUD, experimenting with menus, online dash search, Ubuntu Software Center, etc. -- but they were abandoned. So, if I were to use Ubuntu on my desktop, I would still choose LTS. Read more

Workflow and efficiency geek talks Drush and Drupal

I started using Drupal because I needed an open source content management system (CMS) to use in several community projects. One of the projects I was involved with was just getting started and had narrowed its CMS selection down to either Drupal or Joomla. At the time I was using a different framework, but I had considered Drupal in the past and knew that I liked it a lot better than Joomla. I convinced them to go with the new Drupal 6 release and converted all of my other projects for consistency. I started working with Drush because I wanted a unified mechanism to work with local and remote sites. My first major contribution to Drush was site aliases and sql-sync in Drush 3. Read more