A piece of Rust software I maintain just got a PR attempting to check in a flake.nix and flake.lock. Is this normal, for a Rust package? Do I actually have to put them at in root directory? Is the implication I'd need a flake.guix and guix.lock up there eventually as well? I really hate how modern packaging means like 18 files named like rollup.config.js cluttering the root directory and confusing anyone who just landed on the github page.

@mcc I do use Nix and I would suggest rejecting it unless the author is willing to maintain it

@RosaCtrl @mcc agreed, with the addition that you don't have to accept it even if the author *does* want to maintain it (they can do it outside of your repo)

@whitequark @RosaCtrl Well I was thinking about keeping it in a branch, so that if it grew out of sync I could periodically bump it.

@mcc @whitequark @RosaCtrl for what it’s worth you can also package rust applications on nix without adding files to the original repo, it is just more convenient if you are actively developing on nix

@mcc @RosaCtrl @whitequark (which is to say that if neither you or other major contributors use nix for development it’s probably just gonna be a maintenance headache)