Re: Using the PEAR installer for a non-pear package

Hi Katana, Perhaps the only way to enforce final directory installation is to instruct the user to use the --installroot option to put it somewhere else. Unfortunately, script phase support isn't implemented - this would allow you to run a pre-install script. Otherwise, there will be changes required to the installer (which is a good thing) to make this easy for you. Greg Katana wrote:

Hello, I'm developping a Smarty based forms toolkit (formsess, available at http://www.katana-inc.com/formsess), and I would like to make it possible to install the application using the PEAR Installer. However, a few points are stopping me in that process: - during the package process, I get several errors about the naming not fitting PEAR CS. It is quite logical, since fs was not developped in order to match the CS, and it's even impossible for some functions (there are several smarty plugins, and smarty plugins are prepended with smarty_). - I don't want to have it installed in the PEAR directory, since I don't like cluttering PEAR folder with non-PEAR stuff. So here is the question: what would you recommend ? Katana