Hi, If your end users do the install rather than having everything packaged up in Cava, they get a working Perl + Wx + no restriction on plugins etc.
Cava = distribute application - maybe closed source - can't run any non-packaged Perl (by design). I'm sure this will break an attempt to package Padre in one way or another. Citrus = distribute and re-distribute a predictable Perl + Wx to run your open Perl code on. No need for Cava. Fully open source. I'm pretty sure you want the pure Citrus approach. There are some issues for Citrus regarding CPAN clients that make assumptions about the Perl they're running in but eventually I'll trawl the docs for each and figure out setting up an environment to make them play nice. For now, good ole 'cpan' is your friend. Since I started writing this, a couple more list posts arrived. I'm currently working on a Linux installer for Cava. It is a gui for requesting install location + installation of menu items and icons in standard free-desktop locations. I'll be able to stub a Citrus install with it. In preparing Citrus, I build on Red Hat alike CentOS5 - which contains minimum glibc + gtk I want to work with. I then test it to ensure it works with all the distros I claim it does. If you build your Padre on Ubuntu 10.10, for example, you'll likely pick up dymanic loading dependencies via built xs modules that are going to prevent your xs modules running on older distributions. So, if you go down the route of pre-building everything, I'd suggest CentOS5 as a platform. Seems to me your best option is to tell users to chmod 0700 citrusperl-linux-x64-5-12 ./citrusperl-linux-x64-5-12 -d /pathtoinstall /pathtoinstall/CitrusPerl/x64/5-12/bin/citrusreloc . /pathtoinstall/CitrusPerl/bin/citrusenv64 cpan -i Padre Eventually, I'll wrap this in a gui to request install path. Regards Mark On 24/02/2011 18:50, Claudio Ramirez wrote: > On Thu, Feb 24, 2011 at 7:43 PM, Mark Dootson <mark.doot...@znix.com > <mailto:mark.doot...@znix.com>> wrote: > > Hi, > > Citrus Perl is a much better choice for this both technically and from > an OS perspective > > > Yes, sorry, I wasn't very clear. This is what I did: > First I downloaded Citrusperl, then I installed padre from its cpan > client (like you write on the webpage). Then I pointed the Cava packager > to the main padre script and added some modules manually (that weren't > detected by the packager). > > Claudio > > > > _______________________________________________ > Padre-dev mailing list > Padre-dev@perlide.org > http://mail.perlide.org/mailman/listinfo/padre-dev _______________________________________________ Padre-dev mailing list Padre-dev@perlide.org http://mail.perlide.org/mailman/listinfo/padre-dev
