From owner-freebsd-questions@FreeBSD.ORG Mon Jul 17 23:17:42 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8E48716A4DA for ; Mon, 17 Jul 2006 23:17:42 +0000 (UTC) (envelope-from bob@tania.servebbs.org) Received: from mail1.panix.com (mail1.panix.com [166.84.1.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0B30743D46 for ; Mon, 17 Jul 2006 23:17:41 +0000 (GMT) (envelope-from bob@tania.servebbs.org) Received: from mailspool2.panix.com (mailspool2.panix.com [166.84.1.79]) by mail1.panix.com (Postfix) with ESMTP id 3B81258842 for ; Mon, 17 Jul 2006 19:17:41 -0400 (EDT) Received: from [192.168.1.100] (pool-71-247-67-41.nycmny.east.verizon.net [71.247.67.41]) by mailspool2.panix.com (Postfix) with ESMTP id 0EC24438720 for ; Mon, 17 Jul 2006 19:17:40 -0400 (EDT) Message-ID: <44BC1A90.9090206@tania.servebbs.org> Date: Mon, 17 Jul 2006 19:17:36 -0400 From: Bob User-Agent: Thunderbird 1.5 (X11/20060628) MIME-Version: 1.0 CC: freebsd-questions@freebsd.org References: <44BA98A9.9040903@tamara-b.org> <17594.43423.928991.591165@bhuda.mired.org> <44BACE63.9030800@tania.servebbs.org> <17595.42791.720165.478108@bhuda.mired.org> <44BBFE49.4080602@tania.servebbs.org> <17596.3659.286257.639099@bhuda.mired.org> In-Reply-To: <17596.3659.286257.639099@bhuda.mired.org> X-Enigmail-Version: 0.94.0.0 OpenPGP: id=B2BF9879 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: LinkLib Issues In freebsd Lazarus X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jul 2006 23:17:42 -0000 Mike Meyer wrote: > Well, one solution is to distribute sources - which works especially > well if you provide a port. See below for more on that. > Yes, but the sources Makefile would have to be not only version aware, but also "port-status" aware as well, and then call ld with the proper args. Worse, if 6.5 comes out, and the libs are renamed to libgdk.1.2.0 for instance, then no one will know what to look for until something breaks. > If you want to distribute binaries, you could simply include the > correct libraries in your tarball, and only install them if they > aren't installed. > Actually, my first thought would be to check whether or not the old lib-name was there, and, if so simply ln -s old-lib new-lib via the install script; something I believe the development team should have done when they changed the names, simply to maintain backwards compatibility. However, I don't know what effect this would have on a port upgrade, (I am a newbie on day 10 of FreeBSD) if the upgrade finds the new-lib-name as a link? Barf-Time? FreeBSD is not limited to software available through the ports collection alone, nor should it be. > I'm just trying to point > out some ways you can deal with it. > Yes, and thanks! I think I will ask what the lead time is on the FPC-2.0.4 release. If it will be soon, and if this issue is resolved, then I will simply start over at that point :-) Otherwise, I will have to rethink how to deal with this in the long run. Thanks for your many suggestions, and for your help! Bob