svn commit: r476670 - in head/devel: . rubygem-solve
Alexey Dokuchaev
danfe at FreeBSD.org
Fri Aug 10 10:10:55 UTC 2018
On Thu, Aug 09, 2018 at 07:30:28AM -0500, Mark Felder wrote:
> Adam, please stop. You cannot honestly expect committers to invent
> descriptions for ports that have zero documentation.
Of course we can; in fact, that's their direct responsibility. If one
had ported a piece of software, they are expected to know when does it
do or why is it useful to have in the collection, and be able to express
this knowledge in a few sentences. I utterly fail to understand what's
so hard about this?
> I have plenty of ports myself that only exist in the tree because I
> had to chase dependencies for the software I intended to port. Most of
> these are libraries that have non-descript or "too-clever" names and
> of which I have no idea what their function is.
So you're bringing potentially dangerous or malicious software in the
collection, how nice.
> It is not my responsibility nor the responsibility of any committer
> to fix this problem.
It is your and others' direct responsibility if you offer a piece of
software to our users. You don't have to audit the entire source code
but at least basic understanding of what are you adding is certainly
in order.
./danfe
More information about the svn-ports-all
mailing list