Date: Wed, 18 Jul 2018 12:05:12 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 229846] update net-im/py-matrix-synapse to 0.32.2 Message-ID: <bug-229846-7788-NVuBqPvZzK@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-229846-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-229846-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229846 --- Comment #3 from Kubilay Kocak <koobs@FreeBSD.org> --- (In reply to Markus Mann from comment #2) Python ports should declare/match the dependencies declared by upstream, as closely as possible, without being incorrect. Upstream is the best and canonical source of this information.=20 More broadly and specifically, a port should depend on exactly everything t= he software (code) uses *itself*. Whether or not another dependency of that software depends on it too or not is not a consideration.=20 In summary, it either depends on it, or it doesn't. If it uses it, it depen= ds on it. If spurious dependencies are identified (a declared dependency that is not actually used), then it should be reported and fixed upstream as a first co= urse of action. *optionally* it can be not included, or removed, and/or commente= d as such in the port until the change is released in subsequent versions. Howev= er ... The support burden for not having dependencies (or anything else for that matter), exactly as declared by/in upstream code is on the person(s) making that decision, and since the spurious dependency downside is minimal in most cases (all else being equal), it is not worth doing (and maintaining that discrepancy) in favour of just correcting the issue upstream. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-229846-7788-NVuBqPvZzK>