On Wed, 15 Aug 2007 13:18:11 +0100
Christopher Key <[EMAIL PROTECTED]> wrote:

> I've gone for a portconf based solution for now, although, when I get 
> the chance, I'll try to test how portupgrade behaves wrt
> dependencies.

Please don't forget to try switching to portupgrade-devel in that case.
According to /usr/ports/UPDATING recommendations (20070519):

  # portupgrade -f -o ports-mgmt/portupgrade-devel portupgrade
  # ...
  (etc., do the rest in order to rebuild /var/db/ bits and to build or
  fetch the new INDEX.)

If dependencies bug ever really existed (I can't remember that anyone
confirmed that offering an example), it was related to non-devel

> I would prefer to use pkgtools.conf for several reasons:
> 2) MAKE_ARGS get echoed when things are being built, whereas
> arguments in make.conf don't seem to

Agree here, this is sometimes the only 100% sure method to know how the
binary in question was really built.

Nikola Lečić
freebsd-questions@freebsd.org mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to