[php-maint] [PATCH] New way to handle extensions
seanius at debian.org
Tue May 29 06:46:40 UTC 2007
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
> 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
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.
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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://lists.alioth.debian.org/pipermail/pkg-php-maint/attachments/20070529/d35c01d0/attachment.pgp
More information about the pkg-php-maint