This needs to target staging.

cc @volth @dtzWill

@veprbl rebased onto staging

I am not very happy with bloating buildPerlModule/buildPerlPackage in order to fix less than 0.1% of its use cases. Those could be addressed either in buildPerlProgram or just by adding single line (wrapProgram or patchShebangs) in the derivation's postInstall.

I don't understand how introducing buildPerlProgram is going to help reducing the bloat here. You want to move shebang patching out from builder.sh? If yes, then I think that this is an orthogonal problem. It is not introduced by this PR, the code for patching shebangs is already in the builder.

The single line in postInstall would be needed for 0.1% of packages which may be, say, 10 to 20 of identical lines across nixpkgs. I thought this was the reason why we are trying to refactor this into an option for the builder.

Hi @volth, thank you for reviewing this. When I encountered this shebang issue (#35353), my initial instinct was that this shebang injection mechanism should eventually be removed as not robust. If this is the eventual goal, then perhaps the builder.sh bloat can be tolerated as an intermediate step.