I see your point. I know I can build my own packages. I've done that a
few times.
I also  know that's impossible to build all packages with all kind of
options as a binary, but it's kinda frustrating, that such a major
package have all kind of modules like perl, python, ruby and much
more, but is missing an essential one like php.

Z.


2006/1/16, Alan Barrett <apb@cequrux.com>:
> [top-posting corrected]
>
> On Mon, 16 Jan 2006, Zafer Aydogan wrote:
> > 2006/1/16, Lubomir Sedlacik <salo@xtrmntr.org>:
> > > you are confusing two issues here.
> > >
> > > it *is* possible to install PHP Module for Apache 2 as a binary packa=
ge.
> > >
> > > such a package isn't provided on ftp.NetBSD.org because currently the
> > > bulk-build framework builds everything with the default set of option=
s
> > > and the default Apache version is 1.3.x.
>
> > you say it is possible, but there is no package -- then it is not
> > possible. you are contradictory.
>
> Zafer, you are still confusing two issues here.
>
> 1) Does the pkgsrc and/or pkg_add framework allow a binary package of
>   ap-php4 to depend on apache-2.*?
>
> 2) Are there any pre-built binary packages on ftp.netbsd.org that were
>   created in such a way that the binary package of ap-php4 depends on
>   apache-2.*?
>
> The answer to (1) is: Yes, but you have to build the binary packages
> with non-default options.  You are free to do that yourself, and
> distribute your own binary packages to multiple machines under your
> control.  Then when you pkg_add your own special version of the ap-php4
> binary package, it will install apache-2.* as a dependency.
>
> The answer to (2) is: No, the binary packages on ftp.netbsd.org were all
> built with default options, and that implies apache-1.3.*.
>
> So, it is possible, but somebody else did not do it for you.  There's no
> contradiction in that.
>
> --apb (Alan Barrett)
>