From owner-freebsd-ports@FreeBSD.ORG Fri May 2 16:42:15 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 F28E837B401 for ; Fri, 2 May 2003 16:42:14 -0700 (PDT) Received: from main.gmane.org (main.gmane.org [80.91.224.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id F13BC43FB1 for ; Fri, 2 May 2003 16:42:13 -0700 (PDT) (envelope-from freebsd-ports@m.gmane.org) Received: from root by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 19Bk8m-0005Rq-00 for ; Sat, 03 May 2003 01:40:32 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-ports@freebsd.org Received: from news by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 19Bjvi-0004nc-00 for ; Sat, 03 May 2003 01:27:02 +0200 From: Henrik Motakef Date: Sat, 03 May 2003 01:35:33 +0200 Lines: 21 Message-ID: <87ade4udkq.fsf@interim.henrik-motakef.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@main.gmane.org User-Agent: Gnus/5.090016 (Oort Gnus v0.16) Emacs/21.2 (berkeley-unix) Cancel-Lock: sha1:5nCQkxULzNtPhch9onESxwlew0A= Sender: news Subject: Files shared by multiple ports 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: Fri, 02 May 2003 23:42:15 -0000 Hi, I have several ports that are strictly speaking independent of one another. (It's a library compiled for several lisp implementations, and one for the sources.) However, they have one file in common that is used to find and load the library. It is not a good solution to simply install several versions of this file. I also cannot just have each port install the file, scince the first pkg_delete would break all others. There are other ways to handle it, none of which is particularly elegant, like creating a port just for this file the others depend on (seems stupid), or installing it with the source port and have the compiled ones depend on that (I'd rather allow binary-only installations, too). The ideal solution would be to remove this file only when the last port is deleted, for example by querying the package database. Is there a sane way to do this? tia Henrik