cc @volth @edolstra

The one rebuild was ikiwiki, which uses perlPackages.override to pass a modified pkgs set into perl-packages.nix.

I pushed a new version which passes along the pkgs from perl-modules/default.nix to perl-packages.nix to add that possibility again.

Unfortunately I'm swamped with a bunch of other stuff, and also no longer work with Perl, so I cannot review this properly but I agree with the general idea of making the package set extensible.

Rebased onto master to resolve merge conflict.

Rebased again

It allows to recursively override or add a dependency in a perlPackages set:

perlPackages.extend (self: super: with self; {
  ModuleBuild = buildPerlPackage {
    pname = "Module-Build";
    version = "0.4229";
    src = fetchurl { ... };
  };
})

This can also be done with the packageOverrides argument, the same way as in python:

let
  perl = pkgs.perl.override {
    packageOverrides = self: super: with self; {
      ModuleBuild = buildPerlPackage {
        pname = "Module-Build";
        version = "0.4229";
        src = pkgs.fetchurl {
          url = "mirror://cpan/authors/id/L/LE/LEONT/Module-Build-0.4229.tar.gz";
          sha256 = "H+SRps2pFLAbyOWS+qK1QE6fNZFcoVMi+PKo2PkAjBg=";
        };
      };
    };
  };
in
perl.pkgs.CPAN

After looking at the pythonPackages set I just realized that most language package sets are build with lib.makeScope instead of lib.makeExtensible. They function very similar, but lib.makeScope automatically provides a newScope and callPackage function and is specifically made to Make a set of packages with a common scope.

Should I update this PR with a lib.makeScope version? The changes will be very similar.

Only the first code example from above would change from perlPackages.extend to perlPackages.overrideScope', which has the same arguments/effect.

I marked this as stale due to inactivity. → More info

I find myself wanting of this. Are folks still amenable to it being merged after a rebase? @B4dM4n if you’re unwilling I can rebase and open a new PR.