-
-
Notifications
You must be signed in to change notification settings - Fork 14.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
flutter: move build-support/flutter to flutter directory #332623
Conversation
What's the reasoning behind? |
Yeah and if we do this, will rust and other languages/frameworks be moved out of |
Mucho texto: RFC 140 promotes self-contained package directories and strongly discourages files scattered along the filesystem. Things like Further, with the advent of both RFCs 140 and 146, the classification-based package hierarchy is deprecated and should be phased out. Further, and more to the point here, no other files in the whole Nixpkgs call
Well, why not? It is way cleaner and easier to reason about an ecosystem/framework knowing that all its relevant files are concentrated in a single directory tree rather than scattered among a wild, obsolete directory hierarchy. Further, there are some precedents for this approach (yeah, all mine, it is a bit biased I know):
|
fd4b6f6
to
4f3cc18
Compare
4f3cc18
to
dcce48e
Compare
b7d49f5
to
c289f68
Compare
Rationale: With the advent of RFC 140, Nixpkgs becomes to promote self-contained package directories and strongly discourages scattering along the old and deprecated filesystem hierarchy. Further, `build-support/flutter/*` is not referenced by any other expressions in Nixpkgs besides flutter itself. Further, concentrating all Flutter-related toolset below a same directory hierarchy (arguably?) eases maintenance and future migrations.
c289f68
to
a0f3c9a
Compare
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/prs-already-reviewed/2617/1950 |
Description of changes
Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.