Keeping ports updated.

Greeting,

I have a number of jails that require some of the software to be built from ports. I have some questions.

1. With pkg, dependacies are simply installed using pkg. How are dependencies handled when building a port? Pkg? Also built from ports?

2. How do I skip having to press “enter” for every config option? “make -C”?

3. Depending on the answer to 1, how does one keep ports updated with all the options that were selected to begin with?
 
1. With pkg, dependacies are simply installed using pkg. How are dependencies handled when building a port? Pkg? Also built from ports?
See handbook 4.5. Using the Ports Collection , note the "Warning"
Before installing and using the Ports Collection, please be aware that it is generally ill-advised to use the Ports Collection in conjunction with the binary packages provided via pkg to install software. pkg, by default, tracks quarterly branch-releases of the ports tree and not HEAD. Dependencies could be different for a port in HEAD compared to its counterpart in a quarterly branch release and this could result in conflicts between dependencies installed by pkg and those from the Ports Collection. If the Ports Collection and pkg must be used in conjunction, then be sure that the Ports Collection and pkg are on the same branch release of the ports tree.

2. How do I skip having to press “enter” for every config option? “make -C”?
yes | make config-recursive

3. Depending on the answer to 1, how does one keep ports updated with all the options that were selected to begin with?
See handbook 4.5.4. Upgrading Ports, 4.5.4.1. Tools to Upgrade and Manage Ports, and see the manuals of those tools regarding options.
 
Back
Top