diff options
| author | Robert Hensing <robert@roberthensing.nl> | 2021-01-06 13:02:19 +0100 |
|---|---|---|
| committer | Robert Hensing <robert@roberthensing.nl> | 2021-01-06 13:02:19 +0100 |
| commit | a31607f904723295e4dc702c579efd8cc8d7b506 (patch) | |
| tree | 840aa13dbf8cfb442785beca4933cc326c3cb56f /pkgs/build-support | |
| parent | f41f0643f851ce2454958802a21bc48fdd463012 (diff) | |
dockerTools: Don't apologize
Warning about future breaking changes is wrong.
- It suggests that the maintainers don't value backwards compatibility.
They do.
- It implies that other parts of Nixpkgs won't ever break. They will.
- It implies that a well-defined "public" interface exists. It doesn't.
- If the reasons above didn't apply, it should have been in the manual
instead.
Breaking changes will come, especially to the interface. That can be the
only way we can make progress without breaking the image _contents_.
I don't think dockerTools is any different from most of Nixpkgs in
these regards.
Diffstat (limited to 'pkgs/build-support')
| -rw-r--r-- | pkgs/build-support/docker/default.nix | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/pkgs/build-support/docker/default.nix b/pkgs/build-support/docker/default.nix index 276c7cd1bdb8..ae97d5691331 100644 --- a/pkgs/build-support/docker/default.nix +++ b/pkgs/build-support/docker/default.nix @@ -35,7 +35,6 @@ system, # Note: This is the cross system we're compiling for }: -# WARNING: this API is unstable and may be subject to backwards-incompatible changes in the future. let mkDbExtraCommand = contents: let |