Thanks for your replies.
Quote:
Originally Posted by TronDD
pkg_outdated compares to installed ports. So your build machine would need all the ports you use to be installed.
My production systems use few enough ports that I just monitor cvs for changes and rebuild when something I use or depend on changes.
Use proot(1) to keep the ports builds isolated from the build machine's installed packages.
|
I see. Is there some standard way to monitor cvs-changes beside manual looking at / parsing
cvs -qn up ..?
I also wonder if dpb is able to use pkg_add to fetch build-dependencies -
FETCH_PACKAGES=yes in mk.conf seems to have no effect.
Quote:
Originally Posted by jggimi
At 6.3, the tool is out-of-date(1), found in /usr/ports/infrastructure/bin. At -current, this was renamed to pkg_outdated(1), as mentioned above.
|
Thanks, but the build-machine itself will not have any packages installed.