net-p2p/transmission-cli: add CPE and take maintainership

[jbeich]

Summary

• Add CPE information for Transmission ports [1]
• Take maintainership as the next update may require partially reverting rP369657 hacks in favor of upstream support [2]

PR: 197065 [1]
Suggested by: crees (via private unsigned mail) [2]
Approved by: crees (maintainer) [1][2]
Approved by: ??? (mentor)

[jbeich]

• Disable libinotify:
  • used only by transmission-daemon's watch-dir
  • maybe less stable than readdir() fallback
  • disabled by other ports e.g., devel/glib20
  • something completely different from libnotify[1]
• Belatedly bump PORTREVISION

Pointy hat: crees (rP287179)

poudriere bulk -t logs for 10.1 i386:
transmission-cli-2.84_2.log
transmission-daemon-2.84_2.log
transmission-gtk-2.84_4.log
transmission-qt4-2.84_1.log
transmission-web-2.84.log
ditto but with devel/libinotify installed trying to break build:
transmission-cli-2.84_2.log
transmission-daemon-2.84_2.log
transmission-gtk-2.84_4.log
transmission-qt4-2.84_1.log

[jbeich]

CPE change is already under timeout (17 days old bug). The rest needs confirmation/approval from @crees or another timeout.

[crees]

In D1806#7, @jbeich wrote:

CPE change is already under timeout (17 days old bug). The rest needs confirmation/approval from @crees or another timeout.

Approval? I thought I had already, sorry. Anyway, feel free to maintain the slaves too, then approval is automatic.

Chris

[crees]

In D1806#7, @jbeich wrote:

CPE change is already under timeout (17 days old bug). The rest needs confirmation/approval from @crees or another timeout.

Approved.

[jbeich]

Closed by commit rP378806 (authored by @jbeich).

In D1806#8, @crees wrote:

Approval? I thought I had already, sorry.

Ah, you did for CPE change in private mail (i.e. untrackable) from non-freebsd.org address and unsigned. I have slightly higher expectaction around trust for committers, so opened a review to confirm the intent.

In D1806#8, @crees wrote:

Anyway, feel free to maintain the slaves too, then approval is automatic.

It's a bit sad we don't have co-maintainer support. And I'm not optimistic separating maintainership between slaves and master would work e.g., who's responsible on breakage after update.