jesec-rtorrent: 0.9.8-r16 -> 0.9.8-r16-unstable-2023-07-21 #371676
Conversation
github-actions
bot
added
10.rebuild-darwin: 0
vamega
changed the title
There was a problem hiding this comment.
Maybe we should just apply jesec/libtorrent@ed30d71 instead? Not 100% thrilled about shipping a (technically) bleeding-edge build of this for swarm etiquette reasons, especially since this is still a fork.
Open to hearing your thoughts if you actively use the software (though it's OK if you're just interested in fixing it because of the issue!)
|
I'm also considering dropping this package entirely in favor of vanilla, now that upstream has picked up steam again (and downstream/jesec development is stalled). |
@kannibalox If I'm remembering correct, you're a pretty heavy user of rTorrent (correct me if I'm wrong)? Were you ever using jesec's fork (as your PRs to his indicate), and if so, did you switch to vanilla when 0.15.0 was cut? cc @pshirshov for additional thoughts as you've indicated you're a user of jesec's fork as you opened the issue. Is there a killer feature that keeps you on jesec's fork now that upstream has 0.15.0 now? (JSON-RPC and misc. performance improvements I guess?) |
|
I've been using it with flood, so yes, the rpc. |
I'm currently still using my own modified version of jesec's fork, but one of my goals is to get vanilla to point where I don't have to do that anymore (e.g. I just opened a PR for JSON-RPC support). Some of the things compilation things jesec does (linking to mimalloc, compiling with C++17) can still be done on vanilla, if that sounds of interest to you. |
Bumping package to unreleased commit to fix #371518
Things done
nix.conf? (See Nix manual)sandbox = relaxedsandbox = truenix-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.