I added some missing extensions into the EXTENSIONS file
and some missing EXPERIMENTAL files into the extensions
which were marked as experimental.
So every author of those extensions should check that the
information in EXTENSIONS is correct. e.g. There were some missing
info about the primary
On Friday 19 January 2001 16:07, Jani Taskinen wrote:
>I added some missing extensions into the EXTENSIONS file
>and some missing EXPERIMENTAL files into the extensions
>which were marked as experimental.
>
>So every author of those extensions should check that the
>information in EXTENSIONS is co
On Sun, 21 Jan 2001, David Eriksson wrote:
>>BTW. Why does the satellite extension use --enable-satellite??
>>It does use external libraries which are not bundled with PHP.
>>IIRC the --enable-* configure option is meant to be used only
>>with such extensions?? (and satellite relies on some CVS v
hi,
> >>Another thing: Would it be good idea to have the EXPERIMENTAL
> >>text in configure help for such options? This could be automated
> >>in the buildconf ie. it could check if the EXPERIMENTAL is in the
> >>extension's dir and adds the text before/after the option in
> >>the help display..?
On Wed, 24 Jan 2001, Boian Bonev wrote:
>of course. most people don't really bother to read even the configure
>output, i suppose 10% (or less) look into ext/extdir to find
>readme/experimental.
That's true.
>another idea is to have an extension txt help file shown by configure with
>something
