Front page | perl.perl5.porters |
Postings from January 2012
On Wed, Jan 25, 2012 at 3:53 AM, Jerome Quelin <jquelin@gmail.com> wrote: > i'm not the one trying to shave everything possible, since i'm not > working on the installation stage of the distribution. but i think that > for them, every byte count (since it would allow to put more rpms on the > installation cd). and they need perl on the cd since our installer is > written in perl... Out of curiosity, what core modules does the installer use? > in fact, the -devel package only ships all *.h files, and the following > scripts: cpan dprofpp enc2xs h2xs json_pp libnetcfg piconv pl2pm > pod2usage podchecker podselect prove psed pstruct shasum xsubpp Does it ship the libperl.a file? Does it ship the underlying *modules* that those scripts invoke? If so, I'm perplexed at the "savings" of removing just the scripts. > so, is having a p5p stripped down perl with just perl and (almost) no > modules be possible? then we ship this as perl-minimal, all the modules > as perl-$MODULE the way we are doing it for cpan-only modules, and we > create a perl metapackage requiring all the modules that p5p think > should be part of a standard install. I think that's feasible. It will take some work to figure out the dependencies, but Perl already bootstraps its own testing (with a few tricks) so a minimal perl plus deterministic ordering should be possible. -- DavidThread Previous | Thread Next