Date: Mon, 17 May 2010 16:25:13 -0400 From: Wesley Shields <wxs@FreeBSD.org> To: Marcus von Appen <mva@FreeBSD.org> Cc: freebsd-ports@freebsd.org Subject: Re: pylint entry in UPDATING? Message-ID: <20100517202513.GA38026@atarininja.org> In-Reply-To: <20100517201949.GA1613@medusa.sysfault.org> References: <op.vcuotkt7mhpy7y@vova-vaio> <20100517201949.GA1613@medusa.sysfault.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100517202513.GA38026>