From owner-freebsd-ports@freebsd.org Sun Jan 7 21:00:59 2018 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8C1F8E5CF1E for ; Sun, 7 Jan 2018 21:00:59 +0000 (UTC) (envelope-from SRS0=I3Wg=EC=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 52F4778B46 for ; Sun, 7 Jan 2018 21:00:58 +0000 (UTC) (envelope-from SRS0=I3Wg=EC=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id CE88428411; Sun, 7 Jan 2018 22:00:56 +0100 (CET) Received: from illbsd.quip.test (ip-86-49-16-209.net.upcbroadband.cz [86.49.16.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 172B22840C; Sun, 7 Jan 2018 22:00:55 +0100 (CET) Subject: Re: 'pkg upgrade -f spamassassin' stops but doesn't restart spamd To: Eugene Grosbein , Michael Grimm , freebsd-ports@freebsd.org References: <76627A89-D7E9-4010-910B-5F25886E7E7E@ellael.org> <5A523873.2050001@quip.cz> <5A524855.2040901@grosbein.net> <5A5284CC.9050400@quip.cz> <5A528749.9070308@grosbein.net> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <5A528A87.4050908@quip.cz> Date: Sun, 7 Jan 2018 22:00:55 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:42.0) Gecko/20100101 Firefox/42.0 SeaMonkey/2.39 MIME-Version: 1.0 In-Reply-To: <5A528749.9070308@grosbein.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Jan 2018 21:00:59 -0000 Eugene Grosbein wrote on 2018/01/07 21:47: > 08.01.2018 3:36, Miroslav Lachman wrote: > >>> There IS consensus on modifying config files while upgrade and it is written in our Porter's Handbook: >>> only unmodified files may be changes with upgrade. Any other behaviour is a bug that should be fixed. >> >> If it is that simple then tell me how it is possible that for many years there are repetitive discussions >> and many ports with many commits violating this "rule"? > > Because: > > 1) People are lazy and make errors creating ports violating Porter's handbook instructions; > 2) People are lazy and do not create formal Problem Reports even when they are annoyed > hoping that SomeOne (TM) would do that for them. > > Where are your PRs? PRs are false alibi. Some of my PRs are open for more than 10 years. PRs doesn't solve anything even if they have patches. That's why I tried to discuss it publicly. For all erroneous port there must be will on maintainer and committer side. And if "they" think this is not a bug, than why should I spent my time filling another PR which will be left open indefinitely. I will let someone else to fight windmills. Unluckily it is simpler (for me) to maintain private changes to ports tree in local VCS. Miroslav Lachman