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 ...

Ruslan Mahmatkhanov cvs-src at yandex.ru
Fri Feb 17 14:11:08 UTC 2012


Pav Lucistnik wrote on 17.02.2012 18:00:
> On 2012/02/17 14:39, Alexander Leidinger wrote:
>>
>> Quoting Pav Lucistnik <pav at 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.


More information about the cvs-ports mailing list