jgart writes: > Should I keep only one because of propagated-inputs but then doesn't > that break the declarativeness of wanting a particular package without > worrying about dep bleed? > > ¯\_(ツ)_/¯ I also used to run into such problems pretty often. The only way I found to break such cycles reliably (without in the end putting tens of packages into "update also" list) is to create a manifest-file and always install new packages by adding them to the manifest and then installing the manifest: guix package --fallback -k -m ~/fluss-guix.manifest To create the manifest, you can nowadays just export it: guix package --export-manifest > ~/fluss-guix.manifest This works, but is hard to tell newcomers, so I’d much prefer having install show me the list of all other packages that need to be updated to install the package in question and being asked yes or no to that. Best wishes, Arne -- Unpolitisch sein heißt politisch sein, ohne es zu merken. draketo.de