RE: [PEAR-DEV] Questions regarding adding a library

> -----Original Message----- > From: Kelvin [mailto:kelvin@kelvinjones.co.uk] > Sent: Wednesday, February 05, 2003 11:28 AM > To: pear-dev@lists.php.net > Subject: [PEAR-DEV] Questions regarding adding a library > > Hi, > > I currently maintain a PHP library of classes and am interested in > adding these classes to the PEAR repository! > > Obviously PEAR has many pros for adding a class, however in certain > situations (like mine) there are a few cons, for example: > > 1) my library has a farely large user base, and adding it to PEAR would > mean slightly changing the name of each class, thus breaking previous code. PEAR requires that the package meets the PEAR standards. If that is not a feasible path for you someone else will have to make the modifications (so maybe if you put up your code and do some lobbying you can find someone). If you are willing to put even more effort into this you could provide a wrapper for your old user base. > 2) the current library has a single configuration file which sets > certain parmeters for the classes.. how could this be accomodated by PEAR? No functionality for this is planned in PEAR. All packages are supposed to keep their variables, constants etc in their own namespace for all I know. > If I want to add a library to PEAR, should I just branch the current > release into a new set of classes? > > Any comments would be grateful? I do apologize in advance if I have not > been able to articulate the questions that I'm asking myself. Basically the process is that you propose a package that serves a specific purpose. Then people comment on your code and vote if they think it's beneficial to them. So you can't really propose an entire library at once. The voting process will be made on each separate package. Regards, Lukas