How correctly build php subpackages from ports ?

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

How correctly build php subpackages from ports ?

irix
When I try to build one or two subpackages for php 5.3 or 5.2, system
try to build all available subpackages with their dependences. How I can
avoid this ?

I login to /usr/ports/lang/php/5.3  and make show=MULTI_PACKAGES this
show me list available options and when I try to use: env
SUBPACKAGE="-fpm" make install
System build and all subpackages. Iwas very puzzled by this behavior.

Reply | Threaded
Open this post in threaded view
|

Re: How correctly build php subpackages from ports ?

Remco-2
irix wrote:

> When I try to build one or two subpackages for php 5.3 or 5.2, system
> try to build all available subpackages with their dependences. How I can
> avoid this ?
>

(BTW ports related stuff might be best directed to ports@)

I don't think you can.

AFAICT php is one monolithic piece of software that can't easily be built as
separate pieces. The port has as many optional components enabled to
satisfy as many usage scenarios as possible. This means that at build time
you get to build the whole lot.

By subdividing the port into multiple (sub)packages one gets to choose which
individual parts to install, instead of installing everything.

In my opinion you can't expect any convenience from MULTI_PACKAGES at build
time. MULTI_PACKAGES are convenient at install time to give you a choice to
only install those pieces you really need/want.

If you really want to influence the way a port is built, you might want to
create a FLAVOR. But I doubt that's worth the trouble.