From owner-cvs-ports@FreeBSD.ORG Mon May 26 22:51:10 2003 Return-Path: Delivered-To: cvs-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A3FC337B401; Mon, 26 May 2003 22:51:10 -0700 (PDT) Received: from bell.ee.t.u-tokyo.ac.jp (bell.k.u-tokyo.ac.jp [133.11.65.223]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A13D43F85; Mon, 26 May 2003 22:51:09 -0700 (PDT) (envelope-from mita@ee.t.u-tokyo.ac.jp) Received: from micro.if.t.u-tokyo.ac.jp (micro.if.t.u-tokyo.ac.jp [133.11.94.147]) by bell.ee.t.u-tokyo.ac.jp (Postfix) with ESMTP id F3A274594; Tue, 27 May 2003 14:51:07 +0900 (JST) Date: Tue, 27 May 2003 14:51:07 +0900 Message-ID: <7vr86l2b04.wl@smtp.ee.t.u-tokyo.ac.jp> From: MITA Yoshio To: Kris Kennaway In-Reply-To: <20030527053136.GA84508@rot13.obsecurity.org> References: <200305262059.h4QKxCFM014664@repoman.freebsd.org> <7vvfvx2c9l.wl@smtp.ee.t.u-tokyo.ac.jp> <20030527053136.GA84508@rot13.obsecurity.org> User-Agent: Wanderlust/2.10.0 (Venus) SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.4 Emacs/21.2 (i386--freebsd) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII cc: MITA Yoshio cc: cvs-ports@FreeBSD.org cc: Kris Kennaway cc: lioux@FreeBSD.org cc: cvs-all@FreeBSD.org cc: ports-committers@FreeBSD.org Subject: Re: cvs commit: ports/Mk bsd.port.mk X-BeenThere: cvs-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 May 2003 05:51:11 -0000 >The patches committed to pkg_tools fix this. However, it loses backward compatibility for those who use all older versions of FreeBSD. I feel the infulence is very severe because majority of FreeBSD users do not necessarily know how to solve this problem with their actual version of FreeBSD. And I myself feel that one can (and tends to) expect a backward compatibility for slight minor version change such as 5.0-RELEASE and 5.1-RELEASE. A RELEASE version becoming incompatible with current ports before the next RELEASE, that is a bit too much for me. Instead, could you please investigate a very, very simple alternative that I proposed? It's just using the /var/db/${PKGNAME}/+COMMENT file, which is ALWAYS correct. Backward compatibility is assured in that case, and until now no I find no negative effect. --- MITA Yoshio