From owner-freebsd-ports@FreeBSD.ORG Fri Aug 3 22:10:14 2007 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 35DDF16A46B; Fri, 3 Aug 2007 22:10:14 +0000 (UTC) (envelope-from bsam@ipt.ru) Received: from mail.kuban.ru (mail.kuban.ru [62.183.66.246]) by mx1.freebsd.org (Postfix) with ESMTP id 93A1513C442; Fri, 3 Aug 2007 22:10:13 +0000 (UTC) (envelope-from bsam@ipt.ru) Received: from bsam.ru ([85.172.12.174]) by mail.kuban.ru (8.9.1/8.9.1) with ESMTP id l73M9qRB099231; Sat, 4 Aug 2007 02:10:03 +0400 (MSD) Received: (from bsam@localhost) by bsam.ru (8.14.1/8.14.1/Submit) id l73MA9O8001944; Sat, 4 Aug 2007 02:10:09 +0400 (MSD) (envelope-from bsam@ipt.ru) X-Authentication-Warning: bsam.ru: bsam set sender to bsam@ipt.ru using -f To: pav@FreeBSD.org References: <52921778@bsam.ru> <1186178328.46188.2.camel@ikaros.oook.cz> From: Boris Samorodov Date: Sat, 04 Aug 2007 02:09:47 +0400 In-Reply-To: <1186178328.46188.2.camel@ikaros.oook.cz> (Pav Lucistnik's message of "Fri\, 03 Aug 2007 23\:58\:47 +0200") Message-ID: <86849396@bsam.ru> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-ports@FreeBSD.org Subject: Re: ldconfig when PACKAGE_BUILDING=YES (and linux ports) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Aug 2007 22:10:14 -0000 On Fri, 03 Aug 2007 23:58:47 +0200 Pav Lucistnik wrote: > Boris Samorodov p=C3=AD=C5=A1e v so 04. 08. 2007 v 01:30 +0400: > > Seems that running ldconfig while building a package at package > > cluster (i.e. when PACKAGE_BUILDING is defined) is quite useless. [1] > >=20 > > To be more specific I'm interested at linux ports. ATM we run linux > > ldconfig (using linuxulator) _at package building_. Hence to create a > > package for FC6 port we should change compat.linux.osrelease (which I > > don't like and try to avoid). If the "ldconfig" stage may be skipped > > when PACKAGE_BUILDING is defined then things get way too easier both > > for default kernel linux.osrelease and default linux_base port change. > I don't follow - what is the problem? An FC6 port can't be build (and more specific -- linux-fc6 ldconfig doesn't run) with current default compat.linux.osrelease=3D2.4.2. So this sysctl should be changed to 2.6.16 for package building sake. When the default compat.linux.osrelease will be switched to 2.6.16 we will get the other way round problem if we try to build and FC4 port. I don't like the status quo and want to find a way to siplify it. WBR --=20 bsam