From owner-freebsd-gnome Mon Jan 28 20:10:35 2002 Delivered-To: freebsd-gnome@freebsd.org Received: from alcatraz.iptelecom.net.ua (alcatraz.iptelecom.net.ua [212.9.224.15]) by hub.freebsd.org (Postfix) with ESMTP id 8E9C637B400 for ; Mon, 28 Jan 2002 20:10:29 -0800 (PST) Received: from ipcard.iptcom.net (ipcard.iptcom.net [212.9.224.5]) by alcatraz.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id GAA88636; Tue, 29 Jan 2002 06:10:27 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Received: from h39.229.dialup.iptcom.net (h39.229.dialup.iptcom.net [212.9.229.39]) by ipcard.iptcom.net (8.9.3/8.9.3) with ESMTP id GAA46056; Tue, 29 Jan 2002 06:10:22 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Subject: Re: dependency question From: Maxim Sobolev To: Glenn Johnson Cc: Tadayuki OKADA , Joe Clarke , freebsd-gnome@FreeBSD.org In-Reply-To: <20020129034418.GA1794@gforce.johnson.home> References: <20020120205118.GA447@gforce.johnson.home> <1011565282.28534.22.camel@shumai.marcuscom.com> <20020120234902.GA74865@gforce.johnson.home> <1011573437.28534.24.camel@shumai.marcuscom.com> <20020121011015.GA20453@gforce.johnson.home> <1011575865.28534.39.camel@shumai.marcuscom.com> <3C518120.CB4F6E71@windriver.com> <20020128015959.GA4082@gforce.johnson.home> <3C552F9E.7284744A@FreeBSD.org> <20020129034418.GA1794@gforce.johnson.home> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-uxDIfhMcHEownhhNfwij" X-Mailer: Evolution/1.0.1 Date: 29 Jan 2002 06:10:02 +0200 Message-Id: <1012277407.45588.39.camel@notebook> Mime-Version: 1.0 Sender: owner-freebsd-gnome@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --=-uxDIfhMcHEownhhNfwij Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Tue, 2002-01-29 at 05:44, Glenn Johnson wrote: > On Mon, Jan 28, 2002 at 01:01:50PM +0200, Maxim Sobolev wrote: >=20 > > Glenn Johnson wrote: > > > > > How does one know what shared-libs are used directly? There are > > > certain libraries that the author specifically mentions along with > > > "must have Gnome-1.4" but the port links every library from gnome, > > > gtk, bonobo, etc. I am pretty sure that not all of these are needed > > > but they are linked into the binary. How can I separate the wheat > > > from the chaff here? > > > > I'm fully agree with the sentiment above. ldd /usr/X11R6/bin/evolution > > shows that the binary is linked with some 50 shared libraries > > (!!!), so that it would be big PITA if we had to specify (and > > maintain that huge list) them all in the port's Makefile. Instead, > > dependency-checking mechanism should be extended to check presence > > of all dependencies, not only those explicitly specified in port's > > Makefile. See my ports/Tools/scripts/chkdepschain.py script and > > GNOME_VALIDATE_DEPS_CHAIN knob in bsd.gnome.mk. >=20 > I just stuck this in my port Makefile. I have ghostscript-afpl > installed and so the dependency checking is failing because it is > looking for ghostscript-gnu. Perhaps we should add `WITH_GS=3D {gnu,afpl,whatever}' /etc/make.conf knob, which would ensure that a correct dependency chain is constructed and a correct version of gs is installed if it is absent.=20 > Should this knob be placed in all gnome ports? Not yet. Right now it is an alpha quality piece of code. However, I'm seriously considering to put it into some BIG ones, like Evolution, Nautilus and so on, because this should drastically reduce number of reports GNOME team receives. -Maxim --=-uxDIfhMcHEownhhNfwij Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQA8ViCZoNu5t4iCBa8RApOsAKCC6w0h/l3nLDyFirtEUt1mqPu6/QCeJyf+ VFpMXsXDPqDPDIk0i7VfS6g= =f6EK -----END PGP SIGNATURE----- --=-uxDIfhMcHEownhhNfwij-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-gnome" in the body of the message