Front page | perl.perl5.porters |
Postings from February 2012
On Thu, Feb 2, 2012 at 2:47 AM, Todd Rinaldo <toddr@cpanel.net> wrote: > 1. Exclude anything dual life in my perl-core package that will conflict with a CPAN version. This is mostly bin scripts. Could you elaborate on why .pm files aren't an issue? (Are your RPMs shadowing the core-installed ones?) > 2. Also strip html docs and man pages as they're duplicate to perldoc. (Is there an opinion on which forms of the docs need to be shipped with the product to comply with the license?) Please forget the "license" question -- I'd really mean "spirit of the license", not "letter of the license". Personally, I think "man" for the bin scripts would be good to have and perldoc for the rest is fine. > 3. Build all dual-life packages individually so they are up to date from CPAN. > 4. make "perl" a meta RPM that simply requires in perl-core and each of the CPAN versions of the dual-life modules. Seems sensible. > IMO, it would be cool if I could somehow tell Configure not to build/install anything that is dual-life. I'm not sure if a non-dual life perl would be stable enough to build the dual life modules if I did that. To me, this is the sanest approach to building out a core perl, allowing for dual-life modules to be updated separately. It's not possible to build everything without dual life modules, since some are essential to the toolchain. I can't see anything preventing only a subset being installed, however. > I don't think I could provide a patch in the short time before the coming code freezes for 5.16, but I was considering taking this project on for 5.18. I'm also not sure how such a patch would be received if I did make it, since p5p would then be providing a way to build a severely stripped down perl. IMO, vendors are doing this anyway, so why not have a sanctioned (maintained!) way to do that. If you are looking to take it on, I would point you to the various "install*" files in the source . They would need a lot of love (or possibly a complete rewrite) to support the ability to install only a subset of what is built. -- DavidThread Previous | Thread Next