On 24/02/2011 20:09, Gabor Szabo wrote:

> I am not sure I understand you.  I don't want our user to
> install CitrusPerl and then cpan Padre.
>
> My hope is that we can package Padre + some of the plugins in
> a stand alone package that the user can install and use regardless of
> which version of Perl she has on the system or if she has any Perl.
> (ok in that case Padre will be just a bloated text editor of course).
>
> For this use case the fact that Padre is written in Perl and that it
> comes with its own perl does not matter.
> We don't want to use this perl for anything else than running Padre itself.

Ahh -

Misunderstanding on my part.

Well, Cava is the correct option then.

For distributable happiness Claudio has the correct approach.
The only thing I would add is to repeat the advice to build on CentOS 5. 
It will get you the widest possible user base for the package.

A question was asked about quickest way to get missing dependencies into 
Cava. Two ways (other than adding each individually)

1) Create a script with a long list of 'require' lines containing your 
dependencies. Add it to Cava project as a script. It is never run, but 
gets scanned for dependencies.
2) Create a global rule for Padre. You probably just need to slurp in 
all the Perl modules under Padre - and scanning those should pick up the 
missing deps.

I imagine you can more easily script the production of a 'requires' list.

Note the facility to run tests against the packaged code. You might like 
to drop in the existing tests and see which work.

Within the next few days I should be releasing Cava with the installer 
capability. Effectively, this runs an 'installer' executable that gets 
packaged with your code. By default it packages a pre defined script 
that just asks for a target location and installs the set desktop / menu 
items. The source for this default installer will be 'open' so you can 
take it as a starting point to create your own more sophisticated 
installer if required.

The Padre project also needs the Cava license for distributing an open 
source project - which you are of course granted - which covers it in 
total I think.

Regards

Mark





_______________________________________________
Padre-dev mailing list
Padre-dev@perlide.org
http://mail.perlide.org/mailman/listinfo/padre-dev

Reply via email to