Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

What is the best approach to avoid conflict among the dependencies from two or more unrelated ports? I'm facing the following problem. A script that I'm using has the follow approach to try to install all dependencies of a port:

assuming $PORTA is pointing for a specific port (/usr/ports/lang/php5 for example)

# Complete dependency chain first
BUILDLIST=`cd $PORTA && make build-depends-list 2>/dev/null`
    # Check to see if item is already built
local _PKGNAME=`make -C $PORTA -V PKGNAME`
if [ `grep -c "$_PKGNAME" /tmp/pfPort_alreadybuilt` -gt 0 ]; then
   echo "    Dependency $BUILD of $PORTA already built on this run.  Skipping."
   echo "    Building dependency $BUILD of $PORTA"
   clean_build_install_clean $BUILD

After it tried to install the whole dependencies, then it will try to install the port.

Is it any better than go through your ports and do a make depends install clean? With the approach listed, I'm having a lot of trouble with minor versions conflicts like perl 5.12.4 is needed, but Perl.14.2 is installed and I have the feeling that make depends make handle it better.

share|improve this question
Did make depends install handle it better? – iyrin Feb 14 '15 at 7:22
FreeBSD ports already will already install all their dependencies before installing themselves. So why are you doing this? – Roland Smith Mar 30 at 10:12

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.