RE: [PEAR-DEV] new C and PEAR extension for php (php-gmime)

> 1. I have seen there is some kind of packaging system > - is there any reliable documentation on using it? Should I use it? It would be good to use it yes. Don't know about firm docs, try http://pear.php.net and looking at the package.xml file in existing packages (http://cvs.php.net/cvs.php/pear). > 2. What name should my extension use? > The C library is called gmime (http://spruce.sourceforge.org/gmime/) > PHP module is then also called gmime.so, > and PEAR classes are called as stated above GMIME_* If your c code ends up in /pear/PECL then I would suggest gmime, whilst the php classes perhaps a Mail_Gmime package. > 3. What type of documentation should I use? There is > xmldoc like documentation now. I used phpdoc > inline comments, should I convert it or not? Docbook seems to be the preferred documentation, with phpdoc commented code. > My perl module is called MIME::Fast (would be > available on CPAN), but now I know > that it would be available as > Mail::Box::Parser::Gmime or something like that. > Should my php extension be available also as > submodule of PEAR Mail or something like similar? As everything is moving to /pear (in cvs) I would suggest creating a Mail_gmime package. I'm assuming that that the current mime stuff will go in there as Mail_mime and the core mail stuff as Mail_(mail|core). -- Richard Heyes "If you have any trouble sounding condescending, find a Unix user to show you how it's done." - Scott Adams