[php-maint] [PATCH] New way to handle extensions
atomo64 at gmail.com
Wed May 30 23:53:05 UTC 2007
First of all I would like to ask you to CC me on message replies as
I'm not in the list (I found the message in the list's archive).
> Yes, the main problem I have with the proposal to turn the conf.d symlinks
> into directories in one swoop is that it leaves a gap where a user can have
> the new version of php installed with an old version of an extension
> package, and either the extension won't be available to the engine or
> removing the extension package will leave behind a symlink that won't be
> cleaned even on purge.
For this I'm quoting my original message:
> And finally (I hope I'm not missing anything ;-) ), I also added a
> per-extension postrm script template that causes all the symbolic
> links to be removed, preventing all those php5 warnings about missing
That postrm script takes care of removing all the symbolic links that
could exist. Of course this action is only performed when the package
is being removed/purged and not when it is upgraded (in order to keep
the extension enabled after upgrading to a new version).
> Although... if we do the symlink->directory conversion at the same time as a
> PHP ABI change, we can sidestep this problem completely. Do we have one of
> those coming up?
How is that?
> Yeah, I don't see any obvious reason why a pre-dep would be needed here.
Ok, let's forget about the pre-dep's.
Atomo64 - Raphael
Please avoid sending me Word, PowerPoint or Excel attachments.
More information about the pkg-php-maint