RE: [PHP-DEV] A suggestion regarding stabel vs. experimental on the extension level
| From: | James Moore | Date: | Sun, 19 Nov 2000 16:38:13 +0000 |
| Subject: | RE: [PHP-DEV] A suggestion regarding stabel vs. experimental on the extension level | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-38502@lists.php.net to get a copy of this message | ||
> Stig Venaas wrote:
> > I like this idea. It should be possible to tag some extensions as
> > experimental and change the status to stable without actually moving
> > anything. One way could be to have an extra check in the separate
> > config.m4 files, or perhaps better, alter config-stubs to only include
> > the config.m4 file if there isn't a file called say .experimental in
> > the extension directory.
>
> as moving files as a CVS user results in loss of history information
> and moving the *,v files on the server requires too much privileges
> i'd agree to the 'marker file' solution
>
> but we should not hide the file, lets call it EXPERIMENTAL or
> even stronger like WARNING-EXPERIMENTAL with some human readable
> information inside and lets have ext_skel create it by default
>
> the information should be as obvious as possible and not hidden
Personally I like the idea of when configuring
using --enable-experimental-mod or --with-experimental-mod this makes it
very clear to the user that it is experimental.
James