mccOct 27
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.
Show threadAndre WeissflogOct 27

@mcc so the same issue like people wanting to add cmake (or other build system files) to random C/C++ projects.

I would reject it. A package management system or build system should be able to work "non-intrusively" (for instance by creating a wrapper git repo which references the original project's git repo as submodule).

Show threadmcc
@floooh I'd tend to view a build system as a different thing from a packaging system.
Oct 27 at 5:18pmWeb
Show threadAndre WeissflogOct 27

@mcc ...and I tend to mix up package- and dependency-management ;)

(but oth, npm dependencies are called 'packages', and the dependency download system in the Zig build system is also called 'package manager' - tbh I'd rather call the Linux system package managers something else...)