-
-
Notifications
You must be signed in to change notification settings - Fork 15.5k
flood: init at 3.1.0 #102552
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
flood: init at 3.1.0 #102552
Conversation
Result of 1 package built:
|
Fixed the license and rebased at 4440ec3. |
/marvin opt-in |
Hi! I'm an experimental bot. My goal is to guide this PR through its stages, hopefully ending with a merge. You can read up on the usage here. |
/status awaiting_reviewer |
@SuperSandro2000 can you review again? |
/status needs_reviewer |
I am not that familiar with node packages. |
Reminder: Please review! This Pull Request is awaiting review. If you are the assigned reviewer, please have a look. Try to find another reviewer if necessary. If you can't, please say so. If the status is not accurate, please change it. If nothing happens, this PR will be put back in the |
3 similar comments
Reminder: Please review! This Pull Request is awaiting review. If you are the assigned reviewer, please have a look. Try to find another reviewer if necessary. If you can't, please say so. If the status is not accurate, please change it. If nothing happens, this PR will be put back in the |
Reminder: Please review! This Pull Request is awaiting review. If you are the assigned reviewer, please have a look. Try to find another reviewer if necessary. If you can't, please say so. If the status is not accurate, please change it. If nothing happens, this PR will be put back in the |
Reminder: Please review! This Pull Request is awaiting review. If you are the assigned reviewer, please have a look. Try to find another reviewer if necessary. If you can't, please say so. If the status is not accurate, please change it. If nothing happens, this PR will be put back in the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
{ pkgs, nodejs, nodePackages, stdenv, lib, ... }: | ||
|
||
let | ||
nodePackagesLocal = import ./node-composition.nix { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can this reuse the shared node packages in nixpkgs? 9000 lines for one package is a bit much.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@timokau I based this on other node packages that are applications too, like this one: https://github.com/NixOS/nixpkgs/blob/e7fe577d9803885d1191c6612b95c246cb605dde/pkgs/development/web/newman/node-packages.nix. There is other examples in nixpkgs too for node packages that brings its full dependency tree.
Why I preferred this approach in this package is that like many things in node ecosystem this package dependencies are always changing. Current master already have a completely different set of dependencies.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
like many things in node ecosystem this package dependencies are always changing
But if you were to just add flood
to the shared node packages, generate.sh
should just add whatever dependencies are required by flood
specifically, while using shared dependencies if available, no?
I'm not actually very familiar with the Node part of Nixpkgs either, I just did this one PR where I merged a lot of Node PRs with merge conflicts. But here I see no reason why flood
can't be handled like all other Node tools.
In fact this PR https://github.com/NixOS/nixpkgs/pull/86776/files seems to try to remove all those other node-packages.json
files
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For context: All the node package definitions actually increase the repository size over time since they get regenerated a lot and each version is kept in git history.
Ok, I will try and see if it works.
…On Sun, Nov 22, 2020, 09:19 Florian Beeres ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In pkgs/applications/networking/flood/default.nix
<#102552 (comment)>:
> @@ -0,0 +1,17 @@
+{ pkgs, nodejs, nodePackages, stdenv, lib, ... }:
+
+let
+ nodePackagesLocal = import ./node-composition.nix {
like many things in node ecosystem this package dependencies are always
changing
But if you were to just add flood to the shared node packages, generate.sh
should just add whatever dependencies are required by flood specifically,
while using shared dependencies if available, no?
I'm not actually very familiar with the Node part of Nixpkgs either, I
just did this one PR where I merged a lot of Node PRs with merge conflicts.
But here I see no reason why flood can't be handled like all other Node
tools.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#102552 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGOEN5QG7GLW3LQPA2TT5TSRD6VRANCNFSM4TICMXZA>
.
|
Closed by: #104735 |
Motivation for this change
This PR adds https://github.com/jesec/flood. As described in the GitHub page:
It goes well with the recently(ish) addition of
rtorrent
as a daemon: #83287Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)