Skip to content
Browse files

added notes about the PECL site conformity

  • Loading branch information...
1 parent 7a038cc commit 9ccde8a41571282521c677edf2b481a526ae03c9 @weltling weltling committed Oct 14, 2013
Showing with 21 additions and 1 deletion.
  1. +1 −1 README.EXTENSIONS
  2. +5 −0 README.EXT_SKEL
  3. +15 −0 README.SELF-CONTAINED-EXTENSIONS
View
2 README.EXTENSIONS
@@ -30,7 +30,7 @@ zend_module_entry foo_module_entry = {
PHP_RSHUTDOWN(foo), /* per-request shutdown function */
PHP_MINFO(foo), /* information function */
#if ZEND_MODULE_API_NO >= 20010901
- FOO_VERSION, /* extension version number (string) */
+ PHP_FOO_VERSION, /* extension version number (string) */
#endif
STANDARD_MODULE_PROPERTIES
};
View
5 README.EXT_SKEL
@@ -31,6 +31,11 @@ HOW TO USE IT
./buildconf; ./configure --enable-module_name; make
+ The definition of PHP_MODULE_NAME_VERSION will be present in the
+ php_module_name.h and injected into the zend_module_entry definition. This
+ is required by the PECL website for the version string conformity checks
+ against package.xml
+
But if you already have planned the overall scheme of your module, what
functions it will contain, their return types and the arguments they take
(a very good idea) and don't want to bother yourself with creating function
View
15 README.SELF-CONTAINED-EXTENSIONS
@@ -153,3 +153,18 @@ ADDING SHARED MODULE SUPPORT TO A MODULE
#ifdef COMPILE_DL_FOO
ZEND_GET_MODULE(foo)
#endif
+
+PECL SITE CONFORMITY
+
+ If you plan to release an extension to the PECL website, there are several
+ points to be regarded.
+
+ 1. Add LICENSE or COPYING to the package.xml
+
+ 2. The following should be defined in one of the extension header files
+
+ #define PHP_FOO_VERSION "1.2.3"
+
+ This macros has to be used within your foo_module_entry to indicate the
+ extension version.
+

0 comments on commit 9ccde8a

Please sign in to comment.
Something went wrong with that request. Please try again.