Created attachment 201734 [details]
Just a couple of questions to understand your motivations.
* If I understand, you creates a new port fos sonar
is because the v3 is a beta version, right?
* Why do you need a beta version instead of the the released one ?
* If you think onece released the new version will replace the v3,
maybe we should rename it soner-devel ?
Thanks for your answers,
^Triage: CC current maintainer of net-p2p/sonarr for feedback on comment 1
v3 is new version of sonarr. It is a major update. Updating from v2 requires database migration, done automatically on supported platforms (i don't remember if that is the case with this port).
It is still in beta and can break from time to time. It has significant improvements over previous version. I personally find these improvements important.
I was just playing with making ports etc and thought that this version isn't there so maybe i can create it. I didn't mean to create any offense to previous version port of the software. This port is largely based on v2 port. If it is not needed then this version can be scrapped since I didn't think about the fact that it is still in beta.
As for naming scheme, v2 has master (stable) and develop (nightly) branches and v3 has phantom (beta) and phantom-develop (nightly) branches. This one is based on phantom-develop branch. After re-thinking about it, I think phantom branch would be a better option for this port.
It probably makes sense from a ports tree consistency standpoint to name this sonarr-devel
I'll get this tested soon
A commit references this bug:
Date: Wed Sep 18 22:50:10 UTC 2019
New revision: 512297
Add net-p2p/sonarr-devel to the tree
The sonarr-devel port tracks the development releases of Sonarr's
v3 phantom branch.
If you previously had net-p2p/sonarr installed, it will automatically
upgrade your database after backing up the v2 database files.
Submitted by: rodrigo
Sonarr3 beta committed as net-p2p/sonarr-devel.
Thanks Rob for the bug report and feld for the commit.