For Windows packages there are also fixes for 32 bit packages on Windows XP 64 and the handling of Perl and modules compiled with the latest gcc versions.

We have taken this step to completely separate the commercial activity of supporting packaging and distributing Perl applications from the actual use of the software. This provides a more flexible and appropriate model for continued development and support.

Commercial support for packaging and distributing your Perl applications is amongst a range of options available from  Znix Services with packages tailored to support your particular requirement.

Cava Packager 2.0.55

Upgrade for all platforms.

Notes for upgrading:

If you are upgrading from a prior version of Cava Packager you should browse the following first:

The initial release will have the modest aim of making it easier to install and update your Citrus Perl installations. The development plan for later releases is to eventually include all of the following:

Now that Win32::Daemon is being supported as part of the libwin32 bundle, installation of the Windows Service module from CPAN or via PPM is straightforward.

Cava Packager provides a sample winservice.pl script that may be used either in part or fully as a basis for your Service Applications. The example script includes event logging using the supplied distributable message dll and fully working install, remove, stop and start command line options.

In view of the availability of a supported and maintained Win32::Daemon module, development of a separate Cava Packager custom Windows Service provider is no longer necessary.

Also added Win32::API to included modules on Windows.

It is an easy upgrade for any existing users - just extract new version over existing version.

Perhaps there will be a more sophisticated installer for Release 3 or perhaps even a Citrus Perl Manager application.

The major change is the removal of user account functions from the application. These are now handled at https:/www.cava.co.uk. Cava is a commercial application and needs some way for end users to manage installs. It turns out no-one really liked the application based management and secure background interaction it involved. So it is now gone from the application together with all remnants of SSL remote access. There are still a couple of simple http get functions that check for version and rule updates, but that's all.

There will always be free use for free beer non commercial applications. All that non-commercial users now need do is register once at the web site and download their free use keys. Renewal will be required once every 12 months just like commercial users, but the non-commercial option will remain available for eligible users and usage.

The Linux installer is now at a stage where simple but fully functional installers can be created. There is much more that could be done here to create a rich and fully featured installer but that will have to wait. The installer code is open though so anyone wishing to create a more sophisticated installer can do so using as much or as little of the existing code as they wish.

Next up is an update release of Citrus Perl to include updated wxWidgets and Wx together with a few extra management and configuration features. Then a Citrus Perl Manager applet for Cava Packager to ease installation, maintenance and update of Citrus Perl installations.

Additional features include the provision of a customisable installer for Linux deployment and the restoration of Inno Setup libraries for Windows as were provided in version 1.3.  Mac OS X users are well catered for by the Xcode PackageMaker application.

Interesting bug fixes include tackling some environment related issues on Windows and fixing __DATA__ handling problems in some modules when packaged in the virtual file block.

The Rule engine has been expanded and the opportunity to write your own custom rules enhanced and documented.

A big thank you to everyone who contributed feedback on the prior release and new features. 

The goal is a fairly common interface for the types of things you may wish to do in an installer such as displaying a license and installing desktop and menu features which is then tailored for platform differences.

On Windows we shall be returning to the inclusion of the excellent InnoSetup engine with the application as it was in Cava Packager 1.x. We'll be including a few extra settings options in the Cava Packager interface this time which should cater for most users needs. There is always the option to use the full InnoSetup installation from http://www.jrsoftware.org if you require finer control and more advanced options.

On Mac OS X the current recommended method of simply distributing a .dmg is wonderfully simple for gui applications. However, it lacks support for showing a license and may not be suitable for distribution of command line utilities. We'll be making it possible to produce a .dmg with the standard package install layout so that it integrates with Apple's standard pkg handling plus you get standard license agreement and install dialogs.

Edit:

The Apple PackageMaker application turns out to be simplicity itself containing all you might need to bundle applications packaged using Cava. There is little that could be usefully added from the Cava end of things so we have not needlessly extended Cava's capabilities.

We've been working on a prototype installer for Linux applications which uses the Perl capabilities of the application you are distributing to create and run an installer out of a single executable file. It is looking good so far. Setup menu items and icons for the Gnome desktop are working. We've followed FreeDesktop specs so KDE and other managers should work too.

Initially there will be support for a GUI installer if you are distributing a Wx application, and a command line interface if not. In the future we hope to add support for a Tkx based installer GUI. Of course, you can use the Wx based installer with anything - you will just be distributing 10mb of Wx overhead that isn't actually used by your application.

With the release of 2.0.39 smarter dependency scanning and better handling of the 'virtual' directory has much reduced the size of Cava Packaged applications.

The 2.0.39 installer for 32 bit Windows is around 19mb which isn't too bad considering the inclusion of Wx. Some earlier releases with less functionality had touched 25mb.

We do have a prototype virtual file loading system that reduces the size of the current Cava 32 bit Windows release to just below 13mb but it will be some time at least before that makes it into the release tree.

 

The aim of Citrus Perl is to provide a common desktop Perl development environment on the three supported platforms. For this release wxPerl is the supported GUI tookit but others may be added in future releases.

Citrus Perl is released under the Perl Artistic License with no proprietary components so you are free to use it however the Perl Artistic License allows. Some included modules link to libraries that carry their own open source licenses and, of course, wxWidgets is distributed under the wxWindows license.

For Windows users Citrus Perl comes with a bundled gcc compiler from mingw-w64. You may use a Microsoft Compiler with Citrus Perl if you wish.

For users of Strawberry Perl who do not wish to work in Citrus Perl but would like the common set of wxPerl components, a Citrus Pack for Strawberry Perl is provided.

Citrus Perl is available at www.citrusperl.org

It makes sense to have as many users as possible try out Cava Packager for their personal projects which should then feed into increased commercial use. Reworking the non-commercial set-up so that a user account is no longer required removes some unnecessary actions and administration for non-commercial users.

Currently Cava Packager uses on-line registration for all users. The user management modules have been removed from the application.