This might be a stupid question, why is it so difficult to make a static distribution? I was hoping it wouldn't be too hard.
On Sun, Jul 25, 2010 at 7:06 PM, Chris Marshall <[email protected]> wrote: > I think an effort to make PDL build cross-platform, > (as in the goal for PDL-2.4.7) would be *much* more > productive for PDL development going forward. > > If the external dependency issue is resolved, > one could just "cpan PDL". > > At that point, if someone wanted to wrap up and > support a static distribution, (I think it would > be a big effort requiring lots of support and > providing much grief to the maintainers), at least > the PDL part would be relatively easy. :-) > > Cheers, > Chris > > PDL would > On 7/25/2010 6:35 AM, Daniel Carrera wrote: >> Hi guys, >> >> Here is an idea: >> >> * Make a statically-compiled version of the PDL module and shell. >> * Bundle it with the Padre stand-alone distribution. >> * Ship it and call it "Stand-Alone PDL". >> >> Now, like magic, we get the "one click install" we have been dreaming about. >> >> The Padre project already makes a stand-alone distribution that >> includes Perl itself and the core modules. Provided that we can >> statically compile PDL, it seems to me like it should be /easy/ to >> bundle it: >> >> 1. Unzip the Padre distribution. >> 2. Put the PDL directory inside perl/lib >> 3. Put the pdl shell inside perl/bin >> 4. On the top-level directory add two shell scripts: >> - 'pdl' calls the pdl shell with the appropriate parameters and path. >> - 'pdl-ide' calls Padre. >> >> What do you think? >> >> Daniel. > > _______________________________________________ > Perldl mailing list > [email protected] > http://mailman.jach.hawaii.edu/mailman/listinfo/perldl > -- Intolerant people should be shot. _______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
