From owner-freebsd-ports@FreeBSD.ORG Thu Apr 15 11:10:07 2004 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 4B16216A4CE for ; Thu, 15 Apr 2004 11:10:07 -0700 (PDT) Received: from smtp0.server.rpi.edu (smtp0.server.rpi.edu [128.113.53.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id BFB2E43D1F for ; Thu, 15 Apr 2004 11:10:06 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp0.server.rpi.edu (8.12.8/8.12.8) with ESMTP id i3FIA0Ed006430; Thu, 15 Apr 2004 14:10:03 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20040415165435.GB992@schweikhardt.net> References: <200404131516.i3DFGMJA078941@green.homeunix.org> <20040413181311.GA5858@schweikhardt.net> <20040414210630.4353e27c@Magellan.Leidinger.net> <20040415165435.GB992@schweikhardt.net> Date: Thu, 15 Apr 2004 14:09:59 -0400 To: Jens Schweikhardt From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: CanIt (www . canit . ca) cc: Alexander Leidinger cc: freebsd-ports@freebsd.org Subject: Re: ports and DESTDIR (was: Second "RFC" on pkg-data idea for 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: Thu, 15 Apr 2004 18:10:07 -0000 At 6:54 PM +0200 4/15/04, Jens Schweikhardt wrote: >Garance, > ># Another complication is that many ports include cross-references ># to themselves or other programs "on the system". If you install ># to /otherhost/usr/local/bin, then those ports will embed that ># installation path in the files they install. > >No, not when it's done right. PREFIX is not DESTDIR. Sigh. Of course it works when it is done right. EVERYTHING works when it is "done right". But if the original program does not handle this particular issue correctly, and I damn well know some humans have written programs that do not do understand DESTDIR, then it is more work for the port-developer to do. For those few programs which embed paths to other programs, you don't just have to fix the Makefile, you have to fix the actual program. All I meant was that sometimes there is even more work to do, work which porters are not currently doing. I *have* needed to do this work for some programs in the past. It used to come up a lot here at RPI because we run /afs, and we have to install programs into the "read/write" volume, but the programs need to embed pointers to the "read-only" (replicated) volumes. Please stop suggesting that it can not happen. My main mistake in my earlier babbling was to say "many ports" include cross-references. Obviously the vast majority of ports do not embed pathnames to any other programs, and thus this issue does not come up for them. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu