4:
i'm trying to wrap my head around the "big picture" of how this fits
in with the web application policy project. currently, my thought is
that all the php-specific stuff (including pear stuff) should be seperated
into a seperate php policy similar to how there is a perl policy. the web
application policy could then be made to defer most php references to said
policy (with the possible exceptions of required webserver settings etc).
if you haven't read the perl policy, i'd strongly suggest taking a look
at it for ideas of what the debian policy team will want to see.