None of the logic and workflow involved in creating Padre Standalone for Windows is any different to the steps you'd take to built it on Mac or Debian/Ubuntu/whatever.
All you'd need to do is replicate Perl::Dist (or at least, the main steps it does) for either of those platforms, and you'd be done. I've been saying this to whoever would listen for over a year (not just Padre, other places too). It just appears that nobody on Mac or Linux cares enough to bother doing the work. Adam K On 18 June 2010 16:36, Sebastian Willing <sebastian.will...@web.de> wrote: > Hi all, > > I was talking to the Hannover.PM guys about Padre yesterday. All of them are > professional Perl developers and here are their complains: > > --- Padre isn't installable on MacOS --- > Oliver Krüger has been at our CeBit booth and we already failed to run Padre > on his Mac at this time because of the Perl threading issue on Mac. > I'm no Mac user and don't know much about Mac packages but we should really > try to set up a working installation package for Mac which is as easy to use > as "cpan Padre". > I think someone somewhere recently wrote that a .dmg is just a tar archive. > Why not create a standalone .dmg which contains a threaded WxPerl and Padre? > > --- Padre standalone --- > Many of the developers were using Debian without any directly installed CPAN > modules, only Debian packages are allowed at their company (all of them were > from the same company :-) ). > The Padre standalone is 0.55 and contains some bugs and issues which have > been fixed since then. It "didn't work" at all at the guy who tried it but > we didn't talk about detais. He said that he'd try it again before our next > meeting. > > > Creating these packages can't be too complicated. Why not create some kind > of triggerable job (by the release manager) or cronjob which... > 1. Unpacks a prebuild runtime environment (= Perl binary & basic directory > structure, maybe some dependency packages) in a temp dir > 2. Installs Padre including dependencies from CPAN > 3. Creates a distribution tarball/.dbm/whatever (depending on the > environment used in the first step) > > These files might also be checked by automated tests and could be put on the > website as a "release-ly automated build". If they're ok (= running and > no/few/fixed reported problems), they could easily be moved to the main > download page. > > Sebastian > > _______________________________________________ > 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
