diff options
| author | Wolfgang Walther <walther@technowledgy.de> | 2025-09-19 21:07:06 +0200 |
|---|---|---|
| committer | Wolfgang Walther <walther@technowledgy.de> | 2025-09-19 21:07:06 +0200 |
| commit | 4664ae4470091fe7b74040ad730f8039fd737216 (patch) | |
| tree | a049ba7b16384ca61bce6be60ca01cafc276b063 /pkgs/development/python-modules/rangehttpserver | |
| parent | fffba4911c7d70c258dd7008741a97074b841f4f (diff) | |
pkgs/by-name/README: explicitly suggest version specific override interfaces
The current advice of "keeping the override interface" is actively bad,
because it hides certain expectations of a package function in an
undiscoverable place. Ideally, all information about a package is in
one, single place instead.
Version-specific argument names, if required, also have the *benefit* of
creating errors with downstream overrides, much like merge conflicts do.
Instead of possibly silently breaking certain behavior, they make a
change in expectations clear - which might feel annoying when upgrading,
but is ultimately much less problematic down the road.
Diffstat (limited to 'pkgs/development/python-modules/rangehttpserver')
0 files changed, 0 insertions, 0 deletions
