Date: Fri, 17 Feb 2012 18:10:17 +0400 From: Ruslan Mahmatkhanov <cvs-src@yandex.ru> To: Pav Lucistnik <pav@FreeBSD.org> Cc: cvs-all@FreeBSD.org, ports-committers@FreeBSD.org, Stephen Montgomery-Smith <stephen@missouri.edu>, Ashish SHUKLA <ashish@FreeBSD.org>, cvs-ports@FreeBSD.org, Alexander Leidinger <Alexander@leidinger.net> Subject: Re: cvs commit: ports/accessibility/jovie Makefile ports/accessibility/kdeaccessibility4 Makefile ports/astro/kstars Makefile ports/astro/marble Makefile ports/audio/akode-plugins-ffmpeg Makefile ports/audio/amarok Makefile ports/audio/amarok-fs Makefile ports/audio/amarok-kde4 ... Message-ID: <4F3E5FC9.3000103@yandex.ru> In-Reply-To: <4F3E5D9B.1070807@FreeBSD.org> References: <201202161557.q1GFvYRK041580@repoman.freebsd.org> <4F3DB9C9.2070503@missouri.edu> <4F3E4958.2050805@FreeBSD.org> <20120217143931.Horde.nnHOQpjmRSRPPliTKUax9BA@webmail.leidinger.net> <4F3E5D9B.1070807@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Pav Lucistnik wrote on 17.02.2012 18:00: > On 2012/02/17 14:39, Alexander Leidinger wrote: >> >> Quoting Pav Lucistnik <pav@FreeBSD.org> (from Fri, 17 Feb 2012 13:34:32 >> +0100): >> >>> On 2012/02/17 03:22, Stephen Montgomery-Smith wrote: >>> >>>> Also, is there an effective and foolproof method to calculating all the >>>> LIB_DEPENDS? (Remembering that some of the LIB_DEPENDS may depend on >>>> optional settings, and these all need to be considered?) >>> >>> Only sure way to find out would be to run ldd on every binary in every >>> package. >> >> /usr/ports/Tools/scripts/explicit_lib_depends.sh looks which libs are >> recorded as directly required for each binary in an installed port and >> calculates a LIB_DEPENDS based upon this. >> >> When I wanted to change the LIB_DEPENDS to match the output, I was told, >> that the LIB_DEPENDS wass correct, and the it is a bug (in libtool, >> pkg-config and similar ways of obtaining the libs) that additional libs >> are recorded there. > > Yes but that's a somewhat different problem. I'd be happy with > identifying all direct _and_ indirect binaries and bumping their ports, > for now. Still better than relying on Makefile/INDEX metadata.. Dunno, if it's correct, but I'm using beta.freshports.org interface to grab depended port's list. F.e. http://beta.freshports.org/devel/pcre: lists all the ports in "Required by: " field. They are splitted by "for Build", "for Libraries" and "for Run". -- Regards, Ruslan Tinderboxing kills... the drives.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F3E5FC9.3000103>