Op 24-02-11 21:09, Gabor Szabo schreef: > > I am not sure I understand you. I don't want our user to > install CitrusPerl and then cpan Padre. >
A very long time ago I was thinking along these lines: just provide a gtk2 installer wrapper (gtk2 is installed out of the box in Ubuntu and Fedora) that does install some apt-get/yum and cpan behind the curtains. I abandoned the idea because it felt too much like a fragile hack: the chances of cpan getting stuck on one of the modules is pretty realistic. Here is a 5 minute sketch I made then to illustrate what I was thinking: http://home.scarlet.be/var/tmp/assistant2.pl (it's runnable). Citrus brings a lot onto the table. It eliminates the interaction with the system package system (no longer root access!), it has a re-allocable @INC and it includes the by far trickiest dependency (Wx.pm and Wx libs). Despite all this, I really think that for a installer we should stay away from the command line and cpan (== compiling). Even if we use Citrus, we need more than the default Citrus install. If the user has command line moo powers he can easily do an "apt-get install padre" (to get most precompiles dependencies) followed by an "cpan(m) padre". A good Perl developers will learn those things eventually, but we also target beginners. C. _______________________________________________ Padre-dev mailing list Padre-dev@perlide.org http://mail.perlide.org/mailman/listinfo/padre-dev
