Re: RFC: Paths for PHP extensions and libraries
On Sat, 23 Jul 2005, Gareth Ardron wrote:
> sean finney wrote:
> >>extension_dir =
> >>"/usr/lib/php/5.1/20041030:/usr/local/lib/php/5.1:/usr/local/lib/php"
> >
> Forgot to say. At present, *ANY* hand-compiled extension won't be a
> forwards-compatible binary. I've not seen any talk on php-dev about a
> move to make extensions forwards-compatible at all either. As far as I
> understand it, this is because extensions are built around the zend api
> number, so checks are performed on the loading of the module to make
> sure the api numbers match. If they don't, or no api version number is
> found then the module isn't loaded and a warning given out.
Yes, it is true, and it is the reason why I'd love to see some policy
about paths in PHP. Just now there is no possibility to have more than one
version of PHP in the system. There are no standards at all so we will be
first who define them.
BTW, cons for .../php/$VERSION is that there will be just one directory of
higher level (i.e /usr/share/php). I rather would choose perl's schemat
than python's schema.
--
.''`. Piotr Roszatycki, Netia SA
: :' : mailto:Piotr_Roszatycki@netia.net.pl
`. `' mailto:dexter@debian.org
`-
Reply to: