Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 08 Apr 2015 00:08:39 +0200
From:      John Marino <freebsd.contact@marino.st>
To:        "Mikhail T." <mi+thun@aldan.algebra.com>, marino@freebsd.org,  ports-committers@freebsd.org, svn-ports-all@freebsd.org,  svn-ports-head@freebsd.org
Subject:   Re: svn commit: r383538 - head/databases/sqlitemanager
Message-ID:  <55245567.40702@marino.st>
In-Reply-To: <55244DFC.4050609@aldan.algebra.com>
References:  <201504072014.t37KEtvQ028188@svn.freebsd.org> <55243D74.7060009@marino.st> <55244200.9060002@FreeBSD.org> <55244A00.6010702@marino.st> <55244DFC.4050609@aldan.algebra.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 4/7/2015 23:37, Mikhail T. wrote:
> On 07.04.2015 17:20, John Marino wrote:
> Yes, I do think it is better to save a port imperfectly, than to let it
> expire for a silly reason. The port is now better, than it was. If it
> can be improved further, you are welcome to it.

It's not like anybody was complaining about it's deprecation.  Honestly
I'd rather see a port die before seeing it fixed in a half-assed
fashion, especially if you aren't going to stand behind your work.


>> (there it was said *NEVER* use CP to install files, so obviously what
>> you did is not fine.)
> I don't know, John, what your expectations are of the fellow
> ports-maintainers, but I'm not going to review archives of mailing lists
> every time I do a commit. If portlint and other automated checks I'm
> aware of are happy, then so am I.

Part of the discussion is that this particular error may be added to
portlint, but portlint is just a tool.  You are still responsible for
following the PHB regardless of what portlint says or doesn't say. All
the commits are peer-reviewed, so its seems that it's everyone's
expectations that mistakes during the review are fixed and hopefully
those are a one time thing.

John



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55245567.40702>