While updating home-manager I got a notice that freeimage-unstable-2021-11-01 is marked as unsafe.
Since chances are it’s used by something I never use, I’d like to know what I’m using that depends on it… any idea how to do it?
Also… any idea why I have 4 copies of the freeimage stuff in my /nix/store? (I just run nix-collect-garbage -d and the 4 seem to be actually different):
❱ md5sum /nix/store/*freeimage*/lib/libfreeimage.a
67a0ce1cb5dd562473e27d7c88e8a9bd /nix/store/6gi6hm57zngqnxb6p5dnxhjjcbr96lrk-freeimage-unstable-2021-11-01/lib/libfreeimage.a
5995e0affbfa28b63da7e997cb4dbe63 /nix/store/09nwykzzksc0zknflsyxyah5b67c2rsn-freeimage-unstable-2021-11-01/lib/libfreeimage.a
67a0ce1cb5dd562473e27d7c88e8a9bd /nix/store/ikfiv4gpmcpyir7lsj45by653qcnvgyx-freeimage-unstable-2021-11-01/lib/libfreeimage.a
213a408e3c1fbb5dfa4491deebe05984 /nix/store/q2sc85f2hclgwl8m3qdw8rpbs44gzmah-freeimage-unstable-2021-11-01/lib/libfreeimage.a
You must log in or register to comment.
I don’t know why
nixisn’t able to output a plan of stuff it has to do, but anyway, what I’ve done is just install the thing, thennix --query --referrers $storePath. You can do the same with everyfree-image-unstableyou found in your store.Also, you should be able to grep the
.drvfiles for the store paths of eachfree-image-unstableand find out what was passed in to build them. My hunch is that the package was an input to other packages that needed to activate or deactivate build options. Maybe one package needed a specific feature and another needed yet another --> multiple builds.
