Open hraban opened 1 week ago
This fixes a problem I had locally where pinning an Emacs from a previous nixpkgs version in my config didn't also extend to pinning the packages.
I will admit I'm not 100% if I'm solving this the right way but it feels like this is what you'd want? And is this the right way to do so?
Whether this is backwards compatible depends on your interpretation of what the spec was in the first place; was this a bug or a feature?
[ ] Change is backwards compatible.
[x] Code formatted with ./format.
./format
[ ] Code tested through nix-shell --pure tests -A run.all or nix develop --ignore-environment .#all using Flakes.
nix-shell --pure tests -A run.all
nix develop --ignore-environment .#all
[x] Test cases updated/added. See example.
[x] Commit messages are formatted like
{component}: {description} {long description}
See CONTRIBUTING for more information and recent commit messages for examples.
If this PR adds a new module
Description
This fixes a problem I had locally where pinning an Emacs from a previous nixpkgs version in my config didn't also extend to pinning the packages.
I will admit I'm not 100% if I'm solving this the right way but it feels like this is what you'd want? And is this the right way to do so?
Whether this is backwards compatible depends on your interpretation of what the spec was in the first place; was this a bug or a feature?
Checklist
[ ] Change is backwards compatible.
[x] Code formatted with
./format.[ ] Code tested through
nix-shell --pure tests -A run.allornix develop --ignore-environment .#allusing Flakes.[x] Test cases updated/added. See example.
[x] Commit messages are formatted like
See CONTRIBUTING for more information and recent commit messages for examples.
If this PR adds a new module
Maintainer CC