From owner-freebsd-ports@FreeBSD.ORG Tue Apr 22 18:19:10 2003 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B815737B401 for ; Tue, 22 Apr 2003 18:19:10 -0700 (PDT) Received: from hueymiccailhuitl.mtu.ru (hueytecuilhuitl.mtu.ru [195.34.32.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id 47DD443FD7 for ; Tue, 22 Apr 2003 18:19:09 -0700 (PDT) (envelope-from sem@ciam.ru) Received: from ciam.ru (ppp129-90.dialup.mtu-net.ru [62.118.129.90]) by hueymiccailhuitl.mtu.ru (Postfix) with ESMTP id C5E51FAA11; Wed, 23 Apr 2003 05:18:20 +0400 (MSD) (envelope-from sem@ciam.ru) Message-ID: <3EA5EA0D.8070500@ciam.ru> Date: Wed, 23 Apr 2003 05:19:09 +0400 From: Sergey Matveychuk User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru-RU; rv:1.3) Gecko/20030309 X-Accept-Language: ru-ru, ru MIME-Version: 1.0 To: Kris Kennaway , ports@freebsd.org References: <000501c3074c$e5c2be80$0a2da8c0@sem> <20030421210257.GA58574@rot13.obsecurity.org> <3EA48724.3080602@ciam.ru> <20030422001917.GA60080@rot13.obsecurity.org> <3EA53B4A.4030700@ciam.ru> <20030422193337.GA64963@rot13.obsecurity.org> In-Reply-To: <20030422193337.GA64963@rot13.obsecurity.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Recent bsd.port.mk changes X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Apr 2003 01:19:11 -0000 Kris Kennaway wrote: > features enabled ("foo-1.2.3" vs "foo-esound-1.2.3" etc.) This is why > I suggested that comparing the installation prefix and pkg-plist for > overlap with ports that have the same origin may be the only way to do > this reliably. I don't know how to compare pkg-plist files? How to make decision a port is older version and not variant of current one? It must be some evristic method. Some files can be moved in other place, some files can be new, some files can be moved away in new version. In port's variant case path can be changed or file name can be changed (libsome.so and libsome_r.so). In other words, I can't image how it's possible. > To further complicate matters, ports that are moved from one location > to another (listed in MOVED, which can be machine-parsed) are also the > same package, even though they have different origins. It's more easy to image :) -- Sem.