On 12/01/26 15:47 +0100, Leon Timmermans wrote: > On Thu, Jan 26, 2012 at 1:41 PM, Jerome Quelin <jquelin@gmail.com> wrote: > > in fact, the "problem" comes from the fact that perl is shipping > > what is basically an equivalent to a package manager (sthg that allows > > user to fetch updates & install them). > > > > we distributors would like the package manager be our native one, that > > is urpmi/yum/aptitude/whatever. this does not mean that we don't want to > > ship cpan/cpanplus/cpanm/whatever (we do ship them), we just want perl's > > package management to be a fallback if we do not ship a wanted module. > > > > therefore, shipping a minimal perl with no module would allow us to > > compile perl and bootstrap the needed modules, all of them in their > > respective perl-$MODULE package. > > But that does give problems when one isn't in the position to install > packages, for whatever reason. Without the toolchain essentials, one > can not escape from that box. Having to bootstrapping those by hand is > a serious PITA. once again, i'm totally fine to reserve the "perl" rpm to be just a shelf requiring perl-minimal and all perl-$MODULE that p5p think should be part of a standard perl installation. jérômeThread Previous | Thread Next