From owner-freebsd-ports@FreeBSD.ORG  Mon May 17 20:24:43 2010
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 42EC21065670
	for <freebsd-ports@freebsd.org>; Mon, 17 May 2010 20:24:43 +0000 (UTC)
	(envelope-from wxs@atarininja.org)
Received: from syn.atarininja.org (syn.csh.rit.edu [129.21.50.215])
	by mx1.freebsd.org (Postfix) with ESMTP id 1B51B8FC0C
	for <freebsd-ports@freebsd.org>; Mon, 17 May 2010 20:24:42 +0000 (UTC)
Received: by syn.atarininja.org (Postfix, from userid 1001)
	id DF38E5C19; Mon, 17 May 2010 16:25:13 -0400 (EDT)
Date: Mon, 17 May 2010 16:25:13 -0400
From: Wesley Shields <wxs@FreeBSD.org>
To: Marcus von Appen <mva@FreeBSD.org>
Message-ID: <20100517202513.GA38026@atarininja.org>
References: <op.vcuotkt7mhpy7y@vova-vaio>
	<20100517201949.GA1613@medusa.sysfault.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20100517201949.GA1613@medusa.sysfault.org>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: freebsd-ports@freebsd.org
Subject: Re: pylint entry in UPDATING?
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 17 May 2010 20:24:43 -0000

On Mon, May 17, 2010 at 10:19:49PM +0200, Marcus von Appen wrote:
> Hi Vladimir,
> 
> On, Mon May 17, 2010, chukharev@mail.ru wrote:
> 
> > Hi,
> > 
> > It seems than the new version of devel/pylint port is not compatible with the old config files in user's home.
> [...]
>  > Everything work since renaming ~/.pylintrc and ~/.pylint.d. I think this is good to mention in ports/UPDATING.
> 
> personally, I do not think that (incompatibly) changed user options or
> configuration settings for this port are 'worth' an entry in UPDATING,
> thus I skipped it.

UPDATING exists for the cases where manual intervention is required to
continue to use a port. Configuration file changes are one of those
things. I really think we should document this, even if it's not "worth"
an entry in your mind. 

Clearly at least one user was hit by this problem, and being nice to our
users is a good thing.

-- WXS