use Perl

• Antiquated concepts (Score:1)

  by Aristotle (5147)

  I think (part of) the solution is something that came up in the hallways of YAPC::EU a couple of times: de-core most of the modules and dual-life everything that can feasibly be.

  Now it just needs to happen…
  • Re: (Score:1)

    by izut (6269)

    I think another solution would be having the perl modules installed using packaging tools on a different path. Like, adding another directory to Perl's @INC and let that be the place where dual-life modules live.

    --
    Igor Sutton
    • Re: (Score:1)

      by Alias (5735)

      The current split is not necessarily a bad one.
      
      What I just don't understand is why we have dual-life modules install to CORE rather than site, if the module is being upgraded beyond the "core" version that comes with Perl.
      • Re: Antiquated concepts (Score:1)

        by Maddingue (5320)

        We must install dual-life modules in CORE in order for them to be loaded. Otherwise, if we install these modules in SITE, the old version in CORE will shadow the new version. That's what the UNINST ExtUtils::MakeMaker parameter is for (--uninstall for Module::Build). See for example CPAN-RT#22130 [cpan.org].

        --
        Close the world. txEn eht nepO
        • Re: Antiquated concepts (Score:1)

          by Alias (5735) on 2007.09.26 22:49 (#58062) Homepage Journal

          But if SITE is before CORE in @INC, won't they be loaded first?

          Reply to This

          Parent

          • Re: (Score:1)

            by Ron Savage (5224)

            But site is /not/ always before core. And that's a Perl problem big time.
            • Re: (Score:1)

              by Alias (5735)

              The I guess that's part of the "recommended/certified" setup we need to be testing for :)