Yueh-Shun Li

> this PR still seems to big, it adds 4 new functions to `lib.customisation`, each of which supposedly with its own use case. I'd like to see this split into...

Split the Python part into #267296 and #271387. Now this one only focuses on `lib.extendMkDerivation[Modified]`, and is much shorter than it used to.

@ofborg build tests.overriding

I shortly changed the argument `mkDerivationBase` to a function `getMkDerivationBase` yesterday, trying to preserve a `buildPython*` functionality that takes `stdenv` as one of its input arguments to customize its `stdenv.mkDerivation`...

Rebase onto the master branch and try to polish the sentences of the rease-note entry.

Rebas onto the master branch and update the Nixpkgs manual section about fixed-point arguments of build helpers.

@fricklerhandwerk Could you help me take a look at the documentation?

I love the idea of having a unified way to package binaries for MacOS. Regarding the treewide change, 1. `hello: refactor to use darwin.installBinaryPackage` would be easier to read comparing...

It's possible to add features based on third-party libraries while keeping the core functionality self-contained, as long as such dependencies are optional. We could place those features inside blocks guarded...

I'll try to configure `localstatedir` to a path inside the package directory or something. 1. Does it need to be writable? 2. Why is it hard to be dynamically specify...