[q] why drop the flake + flake=false?

[bartbie]

^title
just curious, i know flakes are controversial to say the least but i was wondering if there was an explicit reason; was there some (yet another) broader discussion on discourse or something? is the flake=false some hack to enable shallow fetching them?

also since i'm asking, why not do something like iirc vic does in his templates somewhere where flake.nix just consumes with-inputs?

[mightyiam]

Providing a consumable flake does not benefit the users of this project. All users need is a flake-parts module. If I provide a flake to the user, I would face the problem of flakes not distinguishing between development dependencies and usage dependencies. Which I did in the past; it was added complexity and did not entirely solve the problem 🤷.

[bartbie]

ah makes sense; i've seen people deal with the dev-deps problem by introducing inner dev flake but it sounds cumbersome - i know flake.parts partition feature builds on this pattern so maybe it's not so bad but i haven't personally played with it (yet? 😈).

thx for answer 😎