[php-maint] [PATCH] New way to handle extensions

[Raphael Geissert]

Hello Sean,

On 29/05/07, sean finney <seanius at debian.org> wrote:
> hi raphael,
>
> thanks for spending some time on this!
>
> On Monday 28 May 2007 23:52:21 Raphael Geissert wrote:
> > I've made some modifications to the debian/ files of the php5 source
> > package which are intended to provide a new way of handling the
> > extensions.
> > The current model is /etc/php5/SAPI/conf.d -> ../conf.d
> > My proposition is to make /etc/php5/SAPI/conf.d real directories (not
> > symbolic links) the same way the apache site/mods-enabled directories.
> > So, in order to enable an extension, a symbolic link to
> > /etc/php5/conf.d/extension.ini should be placed in the SAPI/conf.d
> > directory.
>
> i'm open to doing a "conf-enabled" vs "conf.d" approach, but i'm a little
> weary of the specifics in the implementation... if only because we released
> for etch with the current setup, i'd like something that was a little closer
> to that for the sake of consistancy.
>
> in my opinion, i think we should keep the SAPI/conf.d symlinks pointing at
> conf.d, and have a seperate directory where the conffiles go like
> conf-available.d or similar, and then manage the symlinks into conf.d.

I decided to work on a SAPI/conf.d model so different extensions can
be loaded for different SAPI's. Which is useful for hosting services
(for example, to give support for some extensions only when f/cgi is
used). It is also useful for such extensions as php-qt, php-gtk, etc;
which should only be loaded with php-cli.
An other simple example is php-eaccelerator, which only works with mod-php.
There are many examples and reasons why this approach should be used.
I added 'all' as SAPI to make stuff easier when installing a new
extension that may be used in any of the SAPIs.

>
> or, maybe your method is better...  i get the feeling this is mostly a
> subjective matter.  what do other pkg-php people think?
>
> > extensions. And of course, all the other minor change.s like: removed
> > the .links template, modified the SAPI's info on the control file to
> > make them pre-depend on php5-common because this is the package that
> > ships the php5enext and php5disext bash scripts.
>
> i don't think that requires a pre-depends, unless you're doing stuff in the
> preinst/config scripts.  by the time the postinst is run, a normal depends
> should suffice to ensure that the scripts are available.

Oh, ok. Pre-depends isn't needed then.

>
>
>         sean
>
>

By the way, I was thinking about renaming the scripts to
p5enext/p5disext to make them shorter, but I think it is not very
important right now.


-- 
Atomo64 - Raphael

Please avoid sending me Word, PowerPoint or Excel attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html