Perl help needed

Kevin Oberman rkoberman at gmail.com
Sat Mar 31 22:14:14 UTC 2018


On Sat, Mar 31, 2018 at 1:22 PM, Robert Huff <roberthuff at rcn.com> wrote:

>
> Christoph Moench-Tegeder writes:
>
> >  ## Robert Huff (roberthuff at rcn.com):
> >
> >  >    On a system with over 850 ports, 32 starting with "p5-", the
> >  > list of dependent ports portmaster created from
> >  > "pkg shlib -qR libperl.so.5.24" was over 200, including things like
> >  > FireFox and llvm50 (llvm is required for mesa-dri).
> >
> >  That sound like "too much". I've 1408 ports installed, of which 90
> >  are named p5-*, and "pkg shlib -qR libperl.so.5.26" shows only 32 ports.
> >
> >  Did you rebuild everything along the build-dependencies, or does your
> >  build tool use the run-depdendencies?
> >  There had been a time when ports had way too many dependencies
> registered,
> >  if my memory serves right that was because many build-dependencies were
> >  recorded as run-dependencies (or there was no distinction at all). Is
> >  that a leftover effect from those times?
>
>         "Insufficient data, Captain."
>         I followed the instructions for portmaster from
> UPDATING/20171103, only changing the version numbers.
>         Running "pkg shlib -qR libperl.so.5.26" now produces 13 items;
> this makes your explanation plausible, if not authoritative.
>
>         Again, thanks.
>
>
>                                 Robert Huff


While the method in the instructions is  right, it is serious overkill. It
not only lists direct dependencies, but ports that depend on libs or other
executables that link to libperl.

You can save a LOT of time and CPU cycles by updating the obvious
candidates (portmaster p5-) to get almost everything and then using "pkg
check -B" to find all ports that REALLY link to libperl.so.5.24. All I
found was not-snmp (which really IS a perl5 port, but is not prefixed by
p5-) and ImageMagick.

In retrospect, I probably didn't need to re-install most of the p5- ports
as most just call perl5, but have no direct linkages to it. I doubt that
more then a handful of ports actually needed to be touched.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkoberman at gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683


More information about the freebsd-ports mailing list