Re: Several questions regarding new packages

Matthew Fonda wrote:

I am currently working on a package, File_INI, it will be finished soon. This package allows you to easily do many things with INI files, including: get all information from the INI file in an array, get all information from a specific category in an INI file, get a list of all categories in an INI file, get a specific value from an INI file, add values to an INI file, update existing values in an INI file, and new categories and values to an INI file, and convert INI into XML. It is very easy to use, and allows you to quickly and effectively parse and manipulate INI files. Have you looked at the Config package? [1] I think it does exactly what you are trying to do and much, much more, as it supports a wide range of configuration file formats, not just INI files.

So after I finish this and make sure it is as bug free and efficient as possible, and assuming people think this package is a good idea, I take it my next step is to request an account. Are there any things I need to do before requesting an account? Also, is there anything else I should know, being a new author, about requesting accounts and proposing my package?

Here are the steps: 1) Float the idea here on pear-dev. 2) If no one says that there is already a package for that purpose or if you are taking a whole new approach to what an existing package does and/or some people express interest, register for a pear account, briefly describing the package that will beproposed. 3) Open a package proposal using PEPr (the link is on the main menu). 4) Once the package is proposed, comments will be added and you should work through those, responding to suggestions either by adopting them or stating why you don't think they are a good idea, etc. 5) Initiate a call for votes when you are ready. 6) If your package was accepted, register the new package on the PEAR website. (There is a link for "New Package".) and wait for the PEAR group to unlock the package. 7) Also apply for a cvs account from the php-group if you want to use the pear cvs (strongly recommended). It is highly recommended to use the same username for cvs and pear. According to experience, a cvs account takes some time to set up. So be patient about it. You will be able to upload releases regardless of whether the package is in PEAR cvs or not. Once you are a PEAR developer, you will have to do the same thing over again for each new package, with the exception that you don't need to apply for new accounts.

Also, I haven't seen any information saying whether new packages should be coded in PHP5 only, or be compatible with all PHP versions, if possible. Which version is preferred?

Currently, it is preferred if a package is php4/php5 compatible. However, if there is a distinct benefit from being php5 only (exceptions don't count), go for it. Klaus [1] http://pear.php.net/package/Config