I’m seeing warnings like this when I build my system:
collision between
`/nix/store/jr7iy1hb1rkrcijd2m8s65q6rjmgmksk-phonon-backend-gstreamer-qt5-4.9.0/share/icons/hicolor/128x128/apps/phonon-gstreamer.png'
and
`/nix/store/ybnyw6g90zfv9iafy6xf4wqjrjkk3005-phonon-backend-gstreamer-qt5-4.9.0/share/icons/hicolor/128x128/apps/phonon-gstreamer.png'
However, those files are identical:
$ diff -s /nix/store/jr7iy1hb1rkrcijd2m8s65q6rjmgmksk-phonon-backend-gstreamer-qt5-4.9.0/share/icons/hicolor/128x128/apps/phonon-gstreamer.png /nix/store/ybnyw6g90zfv9iafy6xf4wqjrjkk3005-phonon-backend-gstreamer-qt5-4.9.0/share/icons/hicolor/128x128/apps/phonon-gstreamer.png
Files /nix/store/jr7iy1hb1rkrcijd2m8s65q6rjmgmksk-phonon-backend-gstreamer-qt5-4.9.0/share/icons/hicolor/128x128/apps/phonon-gstreamer.png and /nix/store/ybnyw6g90zfv9iafy6xf4wqjrjkk3005-phonon-backend-gstreamer-qt5-4.9.0/share/icons/hicolor/128x128/apps/phonon-gstreamer.png are identical
So, I’m wondering what folks think about modifying pkgs/build-support/buildenv/builder.pl
to compare the colliding files before reporting the collision? (It would remain silent if the files were identical.)
Of course this would be a mass-rebuild, so I wanted to float the idea here before trying to implement and test it.