Re: git: 113cf218fe1d - main - net-p2p/mktorrent: Deprecate and set expiration date to 2025-03-31
Date: Sun, 16 Mar 2025 17:41:27 UTC
On 2025-03-16 11:57, Alexey Dokuchaev wrote: > On Sun, Mar 16, 2025 at 11:49:35AM +0100, Daniel Engberg wrote: >> On 2025-03-16 11:04, Alexey Dokuchaev wrote: >>> On Fri, Mar 07, 2025 at 10:06:59PM +0000, Daniel Engberg wrote: >>>> commit 113cf218fe1d6cf57028bc5e91e3495adea58466 >>>> >>>> net-p2p/mktorrent: Deprecate and set expiration date to 2025-03-31 >>>> Point users to net-p2p/mkbrr >>> >>> Unfortunately, suggested alternative is written in Golang which makes it >>> much heavier to build (I almost run out of my limited disk space waiting >>> for it to download its myriad of go-mod files), and the binary is also >>> considerably larger: [...] >>> >>> So while `net-p2p/mkbrr' is probably a nice project on its own and some >>> might even prefer it, I'd rather stay with good old mktorrent. >> >> You also have net-p2p/intermodal ... >> written in Rust > > Insta-no-no-no, it's even worse than Golang, and by far. > >> I just went with the one that's mostly similar but I can update the >> Makefile. > > No need for the churn, I might throw in some patches collected from > GitHub and/or GNU/Linux packages. > > ./danfe We already have a ton of unmaintained, deprecated, legacy ports that requires time to "keep alive" due to various changes, updates in tree etc, we should really try to avoid adding more to the pile is possible given the lack of manpower or the never ending work depending on how you want to look at it. You have at least 3 alternatives suggested including the unmaintained upstream (upstream is gone) port net-p2p/createtorrent which is very light. The build topic has been touched on before, we don't adapt the tree to build on a potato however I would like to see that we try to optimize builds as much as possible. In this case use binary packages if needed. That being said, I fail to see any practical use case if you have so little capacity to being with so you can't even build one of the mentioned ports let alone running a client. Can't we just let it die and move on? Best regards, Daniel