ports vs packages
cswiger at mac.com
Mon Jan 9 23:16:07 UTC 2012
On Jan 9, 2012, at 2:00 PM, alexus wrote:
> One of the things I'm seeing is that unfortunately packages are
> somewhat limited vs ports...
Packages come precompiled with default options. For people who want non-default options, you would need to build your own package from ports rather than using the precompiled one.
> For example:
> I'm trying to get Apache httpd + PHP to work, after pkg_add -r php5,
> php5 doesn't have libphp5.so that links Apache and PHP together... so
> unless I'm doing something entirely wrong I basically must use ports
> and nothing else to get the functionality i need...
You can use ports and packages together just fine. In particular, you ought to be able to use the Apache-2.x package with a php5 port that you build to enable mod_php.
More information about the freebsd-ports