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
v2ray: init at 4.21.3 #66089
v2ray: init at 4.21.3 #66089
Conversation
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.
otherwise, LGTM
binary seems to work.
maybe add maintainer? :)
Some more changes are made to pass asset files in. |
ping @jonringer |
unfortunately I'm not too experienced with go to know the best practices. Nor do I have commit access :( |
Also, i would squash all the v2ray commits, and have have the maintainer commit come before. Please adhere to CONTRIBUTING.md when doing the commit messages :) |
Rebased with some fix-up |
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/prs-ready-for-review-may-2019/3032/51 |
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.
please squash the commits into two commits, one which adds you, and then 1 for the package
maintainers: add servalcatty
v2ray: init at 4.20.0
if you want the lazy way to do this:
git reset HEAD~6 #dump everything into unstaged
git add maintainers/maintainer-list.nix
git commit -m "maintainers: add servalcatty"
git add pkgs/
git commit -m "v2ray: init at 4.20.0"
git push servalcatty v2ray --force
Squashed and rebased |
''; | ||
}; | ||
|
||
in runCommand "v2ray-${version}" { |
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.
I feel like this could be put into a postFixup
phase.
@kalbasit for his go knowledge
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.
I make this separated to avoid rebuilding the core when assets updated. Assets are data files (like builtin plugins) and I think they should more extensible.
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.
that's fair... just seems like a lot going on within a single file. But I don't feel super strongly either way.
What is blocking this? It has been a while. Can we merge this? |
Upgraded to 4.21.3 and rebased to master. |
Bumped versions of assets and added v2ray service module. |
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.
Sorry for the delay, life has been keeping me quite busy these days.
I left a pair of comments, but looks good overall.
@marsam But since two modules So now I just keep the custom build and install phases. |
@servalcatty thanks for your contribution |
Motivation for this change
v2ray: init at 4.20.0v2ray: init at 4.21.3
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nix-review --run "nix-review wip"
./result/bin/
)nix path-info -S
before and after)Notify maintainers
cc @