nixpkgs/pkgs
Andreas Rammhold cb007e69a1 stdenv: make symlinks that refer to the same output relative
While looking at the graph of all the outputs in my personal binary
cache it became obvious that we have a lot of self references within the
package set. That isn't an isuse by itself. However it increases the
size of the binary cache for every (reproducible) build of a package
that carries references to itself. You can no longer deduplicate the
outputs since they are all unique. One of the ways to get rid of (a few)
references is to rewrite all the symlinks that are currently used to be
relative symlinks. Two build of something that didn't really change but
carries a self-reference can the be store as the same NAR file again.

I quickly hacked together this change to see if that would yield and
success. My bash scripting skills are probably not great but so far it
seem to somewhat work.
2020-01-15 09:26:40 +01:00
..
applications Merge staging-next into staging 2020-01-15 09:23:28 +01:00
build-support stdenv: make symlinks that refer to the same output relative 2020-01-15 09:26:40 +01:00
common-updater
data Merge master into staging-next 2020-01-13 16:08:59 +01:00
desktops Merge staging-next into staging 2020-01-15 09:23:28 +01:00
development Merge pull request #77610 from LnL7/darwin-stdenv-python3 2020-01-15 09:24:57 +01:00
games mindustry: init at 102 (and updates) (#72306) 2020-01-13 18:01:29 +08:00
misc vimPlugins.salt-vim: init at 2017-07-01 2020-01-13 22:49:31 +01:00
os-specific Merge pull request #77610 from LnL7/darwin-stdenv-python3 2020-01-15 09:24:57 +01:00
servers Merge staging-next into staging 2020-01-15 09:23:28 +01:00
shells zsh-autosuggestions: 0.6.3 -> 0.6.4 2020-01-11 12:51:27 -08:00
stdenv stdenv: make symlinks that refer to the same output relative 2020-01-15 09:26:40 +01:00
test
tools ethtool: 5.3 -> 5.4 2020-01-15 09:26:10 +01:00
top-level Merge pull request #77610 from LnL7/darwin-stdenv-python3 2020-01-15 09:24:57 +01:00